tenancy_unavailable: The account's store or mail relay is unavailable
The hosted tier could not open the account's store, or could not send the sign-up or sign-in email. It refused rather than guess. Nothing was changed or created.
What to do
- Retry after a short wait.
- If it persists, contact the operator: the deployment's storage or mail relay needs attention.
On the wire
HTTP 503. Error type internal_error on API requests, sign-up and sign-in; authentication_error on the end-user browser surfaces' JSON answers (widgets, and the top-up page, budget links and portal when they answer JSON).
{
"error": "tenancy_unavailable",
"errorDetail": {
"type": "internal_error",
"code": "tenancy_unavailable",
"message": "the tenant store could not be opened (fail closed)",
"param": null,
"doc_url": "…/errors/tenancy_unavailable.md",
"fix": "the tenant's store could not be opened; nothing was changed — retry, and contact the operator if it persists"
}
}
Only the multi-tenant hosted front door answers this code. The message names what failed: "the tenant store could not be opened (fail closed)" on an API request, "the verification email could not be sent; nothing was created" on sign-up, and "the sign-in email could not be sent" on sign-in. On the end-user browser surfaces the message is "this page is unavailable right now; nothing was changed": the widget routes answer JSON, and the top-up page, budget links and the portal 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.