> ## Documentation Index
> Fetch the complete documentation index at: https://developers.telnyx.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Limits

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](https://developers.telnyx.com/docs/edge-compute/sandboxes/beta-limitations.md).

## Sandbox

| Limit | Value |
| - | - |
| `timeout` | Default 300 seconds, or none |
| Minimum lifetime after a resume | 300 seconds |
| Paused retention | 7 days |
| Environment | 256 variables, 32 KiB per value, 256 KiB in total |
| Tags | 20 per sandbox |
| Readable after termination | At least 30 days |

## Requests

| Limit | Value |
| - | - |
| Request body, except file writes | 1 MiB, then `413 request_too_large` |
| File size | 512 MiB, checked on the request's `Content-Length` before the body is read, then `413 file_too_large` |
| Batch `count` | 1 to 10 |
| Fork `count` | 1 to 20 |
| List page size | Default 20, maximum 100 |
| Lifecycle event page size | Default and maximum 100 |
| `wait` and exec long polls | 10 seconds |
| Token lifetime | 1 hour |
| `Idempotency-Key` | 1 to 255 characters, kept 24 hours |

## Execs and Output

| Limit | Value |
| - | - |
| Exec arguments | 4,096, each at most 131,071 bytes |
| Exec output kept in the guest | The last 8 MiB per exec, for the 32 most recently finished execs |
| Attach messages | 64 KiB of stdin per message, 128 KiB per message |
| Main command logs | 64 MiB per sandbox. Lines over 256 KiB are split. |
| Metrics window | 24 hours per request, at a 60-second step |
| Lifecycle events | Kept 7 days |

## Network and Secrets

| Limit | Value |
| - | - |
| `allow_out` entries | 256 |
| Secret rule hosts | 32 per sandbox, 16 headers each |
| Header template | 2,048 bytes |
| Secret value | 64 KiB |
| Delivered secrets | 16 variables and 16 files, 128 KiB in total |
| Concurrent connections to rule hosts and domain entries | 256 per sandbox |
| Concurrent connections to a sandbox's ports | 256 per sandbox, then `503` |
| Outbound TCP port 25 | Blocked |

## 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.
