Skip to main content
This page lists the product’s limits, per sandbox and per request. A request past a limit is refused with the error named here, never silently reduced. Quotas and sizes that are raised during the beta are on Beta Limitations.

Sandbox

Requests

Execs and Output

Network and Secrets

Idempotency

Idempotency-Key is accepted on every write: creates, batches, lifecycle requests, snapshots, forks, network changes, template requests, execs, kills, stdin closes, file writes up to 8 MiB, file deletes, and renames.
  • Replay. A repeat with the same key and the same request receives the first response, byte for byte, with its status.
  • Reuse. The same key with a different request is refused with 422 idempotency_key_reused.
  • In flight. A repeat while the first request is still running is refused with 409 request_in_progress.
  • Failures. A request that fails stores nothing, so its retry is evaluated again.
A key is scoped to the organization, HTTP method, and endpoint path. Control-plane requests forwarded to the same regional endpoint and direct data-plane requests share the same idempotency scope; the plane itself is not part of the key. Repeating the same method and path with the same key and request replays the first response, while changing the query or request body returns 422 idempotency_key_reused. The request body is compared byte for byte, so a reordered JSON body is a different request.