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

# Quotas and limits

> Workspace quotas, platform capacity, and request-size limits.

Quotas are set per workspace. The error `detail` names your limit and current usage.

## Workspace quotas

| `code`                      | Status | Applies to                                                                                                                                  | What to do                                                                                |
| --------------------------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- |
| `simulation_quota_exceeded` | `429`  | Active Simulations: create, fork, start, and World start. A World start needs a slot for every member at once and starts nothing otherwise. | Stop a Simulation, or wait for a delete to finish. Stopped Simulations do not use a slot. |
| `build_rate_exceeded`       | `429`  | Simulator builds per UTC day.                                                                                                               | Wait for the reset at 00:00 UTC. The response carries `Retry-After` in seconds.           |

Simulator and World builds have separate queues in each workspace. Each queue allows 10 concurrent builds by default. Further requests return `202` with status `pending` and start in creation order when a slot is free. You can cancel pending builds. The quota ledger reports `concurrent_builds` for Simulators and `concurrent_world_builds` for Worlds; pending builds do not use these slots.

Each accepted Simulator build uses one daily build allowance. Queue promotion and retries do not charge the allowance again.

## Platform capacity

`429 simulation_capacity` means Continuous has no free Simulation capacity. It is not a workspace quota. Retry after a short delay.

## Size limits

These answer `413 payload_too_large`:

| Limit   | Applies to                                                                                                                            |
| ------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| 64 MiB  | The `spec` file part of `POST /v1/simulators`.                                                                                        |
| 1 MiB   | The JSON `request` part of `POST /v1/simulators`.                                                                                     |
| 96 MiB  | The whole multipart body of `POST /v1/simulators`.                                                                                    |
| 1 MiB   | The JSON body of `POST /v1/simulations`, `POST /v1/simulations/{id}/fork`, `POST /v1/simulations/{id}/tokens`, and `POST /v1/worlds`. |
| 10 MiB  | An ordinary request body on the Simulation data plane.                                                                                |
| 201 MiB | A `multipart/form-data` request on a Simulation endpoint.                                                                             |
| 268 MiB | A `text/xml` or `application/soap+xml` request on a Simulation endpoint.                                                              |

These are encoded wire-body caps. Vendor file limits and decoded attachment limits can be smaller.

Per-field limits, including names, instructions, filters, and token lifetimes, belong to each generated endpoint schema. A request outside those constraints answers `422 validation`.

## Build budgets

Simulator and World builds use a four-hour budget by default. `timeout_seconds` can select a different budget; the generated build schemas own its accepted range and default. The budget starts when a build leaves its queue. Provider work and validation share the original deadline across retries and recovery. Publication, preparation, and cleanup have separate limits after acceptance. Existing builds keep their recorded deadlines.

Temporary failures can retry within that deadline. A retry does not restart the budget or consume another daily build allowance. A build can still fail before its deadline when its input is invalid or its work cannot continue.