Admin backend unavailable

Identifiers

Field	Value
Type URI	https://echo.labstack.com/pro/problems/admin-backend-unavailable
Code	admin_backend_unavailable
HTTP status	503

HTTP status	English title
503	Service Unavailable

When it occurs

A built-in panel failed to read its quota store, execution store or Stripe export status. The response does not include the backend error.

Client handling

Retry later.

Example response

If your application installs a custom handler, the body may differ.

HTTP/1.1 503 Service Unavailable
Content-Type: application/problem+json
Cache-Control: no-store

{
  "code": "admin_backend_unavailable",
  "detail": "",
  "status": 503,
  "title": "Service Unavailable",
  "type": "https://echo.labstack.com/pro/problems/admin-backend-unavailable"
}

Server correction

Restore the panel backend’s connection, permissions or capacity. For a failed mutation, reload the target before deciding what to do next. A backend error does not mean the change rolled back.

Response fields

Admin console

• code (string, always): The stable code above.
• detail (string, always): The console always sends detail. It is often empty and never contains the underlying error.
• status (integer, always): The HTTP status of the response.
• title (string, always): The HTTP status text, such as Conflict, unless the panel supplies its own title.
• type (string, always): The exact type URI above.

Headers:

• Cache-Control (always): no-store. The console sends it on every problem response, along with its usual security headers.

Notes:

• Fields are written in alphabetical order.
• The console rewrites every 404 response to admin_not_found with an empty detail.

Related behavior

See the admin console for access checks, action IDs and audit failures.