Has anyone experienced issues with serverless /run callbacks since December?
We've noticed that response bodies are empty when using /run endpoints with callbacks in the RunPod serverless environment (occurring sometime after December 2nd).
Additional context:
- /runsync endpoints are working normally
- Response JSON format appears correct in the "Requests" tab of RunPod console under Status
- Our last deployment to this endpoint was two months ago
Could anyone confirm if there have been any releases since December that might have introduced this issue? We haven't made any changes to our deployment since two months ago, but are now seeing empty response bodies with callbacks.
Thanks in advance!
Additional context:
- /runsync endpoints are working normally
- Response JSON format appears correct in the "Requests" tab of RunPod console under Status
- Our last deployment to this endpoint was two months ago
Could anyone confirm if there have been any releases since December that might have introduced this issue? We haven't made any changes to our deployment since two months ago, but are now seeing empty response bodies with callbacks.
Thanks in advance!
