export_budget_exceeded
The hourly budget of PACKAGING WORK for the company is exhausted. This is not a request limit: it counts packaged documents and generated artifacts against the disk and render pool shared by every tenant, so neither spreading the calls nor using another credential changes anything. The `subcode` says which of the two axes ran out — `export_documents_budget` (packaged content) or `export_artifacts_budget` (number of generated files).
| Code | Type | HTTP | Category |
|---|---|---|---|
export_budget_exceeded | rate_limit_error | 429 | Exports |
Cause
The hourly budget of PACKAGING WORK for the company is exhausted. This is not a request limit: it counts packaged documents and generated artifacts against the disk and render pool shared by every tenant, so neither spreading the calls nor using another credential changes anything. The subcode says which of the two axes ran out — export_documents_budget (packaged content) or export_artifacts_budget (number of generated files).
What to do
Wait for the window to roll over — Retry-After says how long — and ask again. A download rejected by a cap, a period with no documents, or an aborted packaging consume NO budget, so retrying after a rejection does not penalise you; downloading an already materialised artifact does not either. If the volume is legitimate and sustained, request an increase of the limit.