Concurrent sandbox quota
A concurrent sandbox quota limits the number of active serverless sandboxes in your organization, shared across users and API keys. Active usage includes sandboxes that are starting or shutting down, as well as those running your code. The following defaults apply when concurrent quota enforcement is enabled. Contact support or your account team to confirm the quota and enforcement status for your organization.
These quotas apply to accounts with sandbox access. An approved quota increase can raise your organization’s limit. If your W&B account type is unavailable or unrecognized, a previously recognized tier takes precedence over the fallback in the table.
The quota check applies to new serverless create requests through the v1 API. Usage from the deprecated v1beta2 API also counts, but v1beta2 create requests aren’t subject to this check. When you integrate quota handling, use the current v1 API.
Quota accounting updates asynchronously. Usage can temporarily exceed the quota, and recently ended sandboxes can take time to stop counting. A concurrent quota isn’t a strict spending cap or a guarantee of available capacity.
Usage counted toward the quota
The quota accounts for the following usage:- Sandboxes preparing, waiting for placement, starting, running, or shutting down.
- Reservations for create requests whose outcome is uncertain, such as a timeout after placement starts.
Handle a quota error
When enforcement is enabled, the quota check determines whether your organization has reached its limit. If so, the platform rejects a new v1 serverless create request with the following error details:
The platform returns the following error message:
concurrent sandbox quota exceeded; request an increase from support@wandb.ai or your account teamHandle the structured error reason rather than matching the message text. Wait for capacity in your quota, then retry with backoff and respect the retry hint. The 5-second hint isn’t a promise that a slot will be available after 5 seconds. Concurrent quota enforcement doesn’t stop sandboxes that are already running, including after a tier change reduces the quota. Other controls, including sandbox lifetime, still apply.
Request a quota increase
To request a higher concurrent quota, contact the team for your account:- W&B customers: email support@wandb.ai or contact your account team.
- CoreWeave customers: contact your account team.
Rate limits
The v1 serverless API also limits how quickly your organization sends create requests and how many create requests it has in progress. These limits are separate from the number of active sandboxes. A throttled create request returns HTTP429 with error reason CWSANDBOX_SERVERLESS_CREATE_THROTTLED. The limit_kind metadata identifies the limit:
Retry with backoff and respect any retry hint in the response. A higher concurrent sandbox quota doesn’t itself increase the rate limits on create requests.
Sandbox lifetime
To limit how long a sandbox can run, set themax_lifetime_seconds parameter when you create it. Lifetime limits apply to both serverless and CKS placement.
If you omit the lifetime, the applicable policy can supply a default. The platform uses 10 minutes when no policy default is set.
The platform rejects a create request that specifies more than the maximum lifetime. The platform stops the sandbox when its lifetime expires. Choose a lifetime that covers the work you need to run, and stop the sandbox when the work finishes.