15 Replies
And webhook does not send.
I'm using Generator Handler (no async)
Thats weird, whats your code like
I'm having the same issue. SDK 1.6.2, 1.7.0 and 1.7.1 all produces this, however very rarely.
Sometimes 1 our of 6, sometimes 1 out of 30.
Re-submitting the same payload can run without issues a second time.
I dont know if that helps, but the 1.7.1 is more verbose with the errors as well :
"payload_size_bytes": 0 <-- seems sus?
Guys try to open a support ticket for this issue and give the example code too
Do you all use .progress_update() by any chance?
On my side, it was added to the code after the above issue started happening. Didn't affect the outcomes
We recently fixed a bug and released it on 1.7.2. The bug caused our platform to disregard workers that are currently working a job. So if a job took longer than an endpoint's idle time (for example) it would put that worker to sleep. By the time the job is finished, it would have no worker to report back to.
Hey @deanQ I've upgraded to 1.7.2 (5-6 hours ago) but still getting stuck jobs the same way. 😦
I have looked at the logs of your endpoint
74jm2u3liu0pcy
. It still says it's using 1.6.2 all week. Could it be a different endpoint ID?Yeah, its
noxhy2en39n3y3
my dev endpoint.not the best of logs. That field actually refers to the size of the body payload on post or put requests. Get requests have none.
I'm not sure i follow 😄
I was referring to this
"payload_size_bytes": 0 <-- seems sus?
It's going to always be zero for GET requests. Payload only exists for post or put requests.Ah, makes sense!