1s delay between execution done and Finished message
I get almost one second of delay between a console message at the end of my handler and the "Finished" message.
I am wondering why, and how to reduce this....
Serverless is Broken
Something is clearly broken. Delay times are around 2 mins even when the same worker is getting a request in a row, it still takes 2 mins. It's not a cold start issue because even my normal cold starts don't take longer than 15 seconds.
Workers wrongfully reported as "idle"
When I call my serverless api endpoint, instead of serving my request, it continues building the image while the worker was reported as "idle" and then "running" when called.
So I cancel the request, but then the only way to make it stop (so it doesn't keep billing me) is deleting the worker....
Incorrect billing
the billing for last 4 weeks seems to be wrong, can someone help me understand. I am using only two serverless endpoints and no other services. Endpoint ids:
ed0rivbjvv0x0u and pzfz3xhwa86raj
Serverles endpoint status and runsync not returning data anymore in request body (request not found)
Hey Team, I have a custom serverless endpoint worker. It always works. The logs always show that everything went as planned and the requests are always marked as completed after the time I expect. However, on my API the requests error out and on the UI they show completed but have no output. When I inspect the status on Thunderclient, runpod says that the request does not exist. I would like to understand what is going on and how I can make my api more resilient to these issues.
Attached are screenshots of the behavior:...
