Does "/runsync" return IN_PROGRESS if it doesn't complete with 2 minutes?
i expect data["status"] to either be failed or success but why does it occasionally do in_progress? I am using the /runsync endpoint
9 Replies
runsync will try it's best to finish when your job is completed, but if it's not done it's just not done :<
Do you expect the job to be terminated if it takes too long? You could always use
run
with webhook delivery to know when the job is complete?Send a request | RunPod Documentation
Learn how to construct a JSON request body to send to your custom endpoint, including optional inputs for webhooks, execution policies, and S3-compatible storage, to optimize job execution and resource management.
what is the default timeout? i'm willing to wait up to 10m on runsync i don't want to use webhooks for now
however it looks like its just timing out after 1-2 minutes
It looks like the delay is 1.5 minutes, 9000ms
I don't think this is documented, and I'm not a Go user so I may be reading this wrong but you can change that by passing a
wait
URL Param as a time in ms (?wait=300000
being the max)
Interesting, it does look like our libraries like runpod-python use this though.i'm using aiohttp i tried using execution policy to 5 minutes but its still timing out around 1.5 minutes is that just a limitation of the runsync route?
The 1.5 minutes a default from our side, without the wait param you can't control how long we keep the connection open from the server side.
If you're using requests:
but the general premise is the same, just add that to the end you'll be fine :)
i'll try this thank you so much (would add to docs for other users)
We're rewriting the docs for clarity, I'll send the docs writer a note to make sure he knows about this feature lol
big w