Timeouts, concurrency and tokens
Limits control different resources. Match them to task duration and size.
| Setting | Controls | Default |
|---|---|---|
MAX_CONCURRENT_SESSIONS | Simultaneously occupied execution slots | 50 |
SANDBOX_PROVISION_TIMEOUT_SECONDS | Initial sandbox creation and connection | 120 s |
run_timeout_seconds | Agent execution time per run | 3600 s |
hooks.timeout_seconds | Each hook's execution time | 300 s |
max_session_tokens | Input and output tokens across all session runs | 100,000,000 |
{
"run_timeout_seconds": 900,
"max_session_tokens": 500000
}This is the value of configuration.limits. Mattermost exposes equivalent workflow fields. max_concurrent_runs additionally limits a workflow's concurrent work.
When global capacity is exhausted, a new request receives 503 capacity_exhausted. Retry later with the same idempotency key. Token budgets rely on agent usage reports and are not exact monetary caps. An exhausted session rejects new runs.
Initial provisioning has its own deadline. If it expires, the run fails with sandbox_provision_timeout. Cancellation during provisioning finishes even when AgentBox requests fail. Orpheus continues looking for the sandbox and deletes it if found. Until deletion is confirmed, its execution slot remains occupied, including after the run becomes terminal. See troubleshooting.
Orpheus renews sandbox activity time during execution. You do not need to manually add hook timeouts to the run timeout. Maximum uninterrupted sandbox lifetime is set by the AgentBox plan.
Account limits show provider quotas separately from these settings.
Paused sandbox retention explains expiration, cleanup and continuation.