Unexpected Infinite Retries Causing Unintended Charges
I recently ran my serverless workload using my custom Docker image on RunPod, and I encountered an issue that resulted in significant unexpected charges. My application experienced failures, and instead of stopping or handling errors appropriately, it kept retrying indefinitely. This resulted in:
- $166.69 charged by OpenAI due to repeated API calls.
- $14.27 charged on RunPod for compute usage.
This behavior is unexpected, as a serverless service should not continuously retry indefinitely without a stopping mechanism. I had to manually intervene to stop the retries, which should not be required. There should be an automatic failure handling mechanism to prevent excessive resource consumption and unintended expenses.
Given that this was caused by an unexpected behavior in RunPod’s execution handling, I kindly request compensation for these unintended charges. Please investigate this issue and let me know how we can prevent this from happening in the future.
I've attached relevant screenshots for reference.
- $166.69 charged by OpenAI due to repeated API calls.
- $14.27 charged on RunPod for compute usage.
This behavior is unexpected, as a serverless service should not continuously retry indefinitely without a stopping mechanism. I had to manually intervene to stop the retries, which should not be required. There should be an automatic failure handling mechanism to prevent excessive resource consumption and unintended expenses.
Given that this was caused by an unexpected behavior in RunPod’s execution handling, I kindly request compensation for these unintended charges. Please investigate this issue and let me know how we can prevent this from happening in the future.
I've attached relevant screenshots for reference.
