tenant_rate_limited: This tenant's request rate is used up
The multi-tenant host refused the request because this tenant exceeded its requestsPerMinute quota. Nothing was billed.
What to do
- Retry after the
Retry-Afterheader (seconds). - If this persists under normal load, raise the tenant's request quota with the operator (quotas are per tenant, never shared).
On the wire
HTTP 429, error type state_error.
{
"error": "tenant_rate_limited",
"errorDetail": {
"type": "state_error",
"code": "tenant_rate_limited",
"message": "the tenant's request rate is used up (fail closed)",
"param": null,
"doc_url": "…/errors/tenant_rate_limited.md",
"fix": "too many requests for this tenant; retry after Retry-After"
}
}
Only the multi-tenant hosted front door answers this code; a single-tenant core has no tenant request quota. Every 429 carries Retry-After: 1. On the end-user browser surfaces the message is "too many requests; retry shortly": the widget routes answer this JSON shape, and the top-up page, budget links and the portal answer a short HTML page naming the code (JSON only to a client that sends Accept: application/json (and not text/html)).
See all error codes.