How long a call can run
A call runs as long as your agent takes, up to the life of its session’s instance: an hour at most. There is no shorter limit on a single call. Your client is usually the limit that matters. Most HTTP clients give up on a response that sends nothing for a while, and a proxy in front of your app may do the same.- Stream long calls. With
"stream": true, Onecortex sends a: pingcomment every 15 seconds while your agent is silent, so the connection never looks idle. - Set your client’s read timeout above 15 seconds, or turn it off, for a streamed call. httpx’s default is 5 seconds.
- A JSON call sends nothing until the run ends, so its read timeout has to cover the whole run.
Onecortex never retries a call
A call reaches your agent once. If it fails, Onecortex does not call your agent again, so a tool with side effects, such as sending an email or charging a card, runs once per request you make. Whether to retry is yours to decide, with that in mind.What to retry
An
event: error in a stream carries the same codes, and the same advice applies.
Back off exponentially from about a second, with jitter, and stop after a few attempts. Every response carries X-Request-Id: log it, so a failure can be matched to your agent’s logs and to support.
Rate limits
Calls are limited per organization and per agent. See Limits. A retry loop that ignoresRetry-After spends the budget faster and fails for longer.