Does /runsync have a timeout?
Hello there. I'm trying to figure out if the syncronous endpoints do have a default timeout.
The doc states that they're "ideal for short-lived tasks", but it only talks about recommendation rather than actual requirements.
Thanks!
24 Replies
Unknown User•15mo ago
Message Not Public
Sign In & Join Server To View
So i could even have an endpoint with
/runsync running for 1-3minutes, as long as my specified timeout is longer than that?Unknown User•15mo ago
Message Not Public
Sign In & Join Server To View
so its going to switch into what /run would be doing?
@nerdylive sorry is there a reference to this in the documentation? I cannot find this anywhere
I find it very difficult to believe that Runpod is doing something like this, is super antipattern
If I call a sync API I should get an error OR a sync response
Unknown User•15mo ago
Message Not Public
Sign In & Join Server To View
I dont find anything about this transformation of a /runsync to /run in the docs, even the AI does not find anything
Another query, I'm almost 100% sure there is no reference to this behaviour in the docs
Unknown User•15mo ago
Message Not Public
Sign In & Join Server To View
I'm sorry but that is not what is stated there
/run will give us a job ID
/runsync will give us the result of the worker
Unknown User•15mo ago
Message Not Public
Sign In & Join Server To View
i think we believe what you're saying, but the point is that we should revise the documentation
because it doesn't state the same
Unknown User•15mo ago
Message Not Public
Sign In & Join Server To View
is not that I dont beleive you, is that we are paying for a service that is not doing what is stated in the docs
can you raise this ticket to second level?
Unknown User•15mo ago
Message Not Public
Sign In & Join Server To View
I dont want to "suggest" I want the company to answer for a miss direction
We'll try the email route then
thanks
Unknown User•15mo ago
Message Not Public
Sign In & Join Server To View
you've been helpful anyways to solve our doubts, at least now we know what to expect đź«
thanks!
Unknown User•15mo ago
Message Not Public
Sign In & Join Server To View
We’ll surely look into using /run + webhooks as the /runsync behavior is completely unpredictable.
After some tests from our end, we believe that the “behavior” switch happens upon 60s of waiting time (worker not ready, queues…) rather than execution time.
Unknown User•15mo ago
Message Not Public
Sign In & Join Server To View
Not really, we managed to get responses after 70s as we had about 35s of waiting time and 35s of execution time. It’s definitely a bit confusing :$
Unknown User•15mo ago
Message Not Public
Sign In & Join Server To View