Managed Backend Tier Configuration Unreadable
URI: https://docs.ankatech.co/errors/managed-backend-tier-unreadable
HTTP Status: 503 Service Unavailable
When you see this
The managed key-protection tier surface could not read its own data — the tier rows or the per-tier tenant count aggregate. It is the only 503 this surface emits, and that exclusivity is the contract: an unresolvable licence never reaches here, because it is reported inside a 200 as licenseState = UNRESOLVED. A 503 on this surface therefore means exactly one thing, and the response carries a Retry-After header.
Common Causes
- The control plane's database is unreachable or refusing connections.
- A data-access failure while reading the managed tier rows.
- A data-access failure while computing the per-tier tenant count aggregate.
Response Example
{
"type": "https://docs.ankatech.co/errors/managed-backend-tier-unreadable",
"title": "Managed Backend Tier Configuration Unreadable",
"status": 503,
"detail": "The managed key-protection tier configuration could not be read. This is a transient condition in the control plane; no configuration was changed. Retry shortly.",
"instance": "/api/v3/admin/platform/key-backend/tiers",
"timestamp": 1730000000,
"extensions": {
"requestId": "550e8400-e29b-41d4-a716-446655440000"
}
}
Content-Type: application/problem+json — the response follows RFC 9457 Problem Details.
How to Resolve
- Retry after the interval the
Retry-Afterheader names — the condition is transient by construction and no configuration was changed. - If it persists, check the control plane's database availability. The body names no tier, backend token, count or schema detail by design; the underlying data-access failure is in the server-side log, correlated by the request id.
- Do not treat this as a licence problem: an unresolvable licence is reported inside a successful response, never as this 503.
For full schema definitions, examples, and interactive testing, see the Developer Hub Reference.