Why is Runsync returning status response instead of just waiting for image response?
My runsync requests are getting messed up by runpod returning a sync equivalent response (with 'IN_PROGRESS' status and id showing). I need to just return the image, or a failure, not the status using runsync. If I want the status I would just use 'run'. Any idea why this is happening and how to prevent it?
For reference, this is for request that generally run for 5-18 seconds to completion.
delayTime: 196
id: "sync-dad6d689-1106-4f29-9aea-a843c6741687-u1"
status: "IN_PROGRESS"
workerId: "0q4lddfhys3oxk"
4 Replies
Because the job took too long to process
So it returns after like a minute
You need to call status after that
So it's better to use /run for this use
So I implemented GET polling to fix, but it's weird that this happens even after just 15 seconds of waiting sometimes. A minute would make sense, but it seems to be happening way too fast for a true sync request.
Oh 15secs?
Maybe runpod team can check it I'll open a ticket
@bossman
Escalated To Zendesk
The thread has been escalated to Zendesk!