Quotas and backpressure

Capacity controls protect interactive Studio work, partner fairness, object storage and processors. Limits are authenticated-account configuration and may differ by reviewed plan or rollout.

Request

Rate-limited requests return 429. Honor Retry-After, add jitter and reduce concurrent retries. Do not distribute one logical sender across credentials to bypass account limits.

Upload

Upload concurrency and reserved bytes are tracked separately from manifest acceptance. Complete or expire unused intents promptly so reservations can release.

Jobs

Active-job and processor-budget limits prevent a large catalog from consuming all worker slots. Accepted durable work remains visible while it waits for capacity.

Items

Manifest byte and item limits keep validation bounded. Split large catalogs into stable, idempotent messages while preserving sender refs and release integrity.

Fairness

Bulk senders do not consume capacity reserved for creator-facing Studio work. Capacity policy is enforced by the service; client-side throttling complements but cannot replace it.

429

Inspect the stable code, unit, current, requested and limit values where supplied. Some capacity errors are retryable after time or state changes; structural size limits require splitting or a reviewed plan change. See Errors.

200-track pilot

The guided interface may present a bounded rollout such as a 200-track batch while the canonical system is designed for many immutable batches and much larger catalogs. Do not treat a pilot UI boundary as a universal API promise.