Sync endpoint returns prematurely

Sync endpoint sometimes randomly (about half of the time) responds prematurely with in progress json. The job finished however, I need the sync not to respond until the job is done.

Jason•8/23/24, 2:23 PM

Oh its because your job runs longer than 60s

Jason•8/23/24, 2:23 PM

then it'll return in_progress

Jason•8/23/24, 2:24 PM

so, its better to use webhook back to your server(read docs), or use /run + pinging /status every once in a while or some other delay you can custom

abtxOP•8/23/24, 3:04 PM

OHh so If I keep pining the connection will stay alive?

Jason•8/23/24, 3:37 PM

No, it will return in progress or completed

Jason•8/23/24, 3:37 PM

But since you are pinging constantly, you will get updated status when you ping it

Jason•8/23/24, 3:38 PM

If you use webhook it will reach out to your server when it's done

Jason•8/23/24, 3:38 PM

Depends which you would use

abtxOP•8/23/24, 3:39 PM

How do I force the connection to stay longer? @nerdylive Currently our architecture doesnt support async

abtxOP•8/23/24, 3:39 PM

Just need temporary quick solution to use /runsync

Jason•8/23/24, 3:59 PM

Ah, thats impossible unfortunately

Aabtx How do I force the connection to stay longer? @nerdylive Currently our architect...

Jason•8/23/24, 3:59 PM

well, make your do.. there are 2 ways as i noted above

Jason•8/23/24, 4:00 PM

i don't think there is such if your run is long

yhlong00000•8/23/24, 8:10 PM

you can use webhook, after job done, it will notify you with result.
https://docs.runpod.io/serverless/endpoints/send-requests#webhooks

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.

Sync endpoint returns prematurely

Similar Threads

Similar Threads

Similar Threads