Admin busy

Identifiers

Field	Value
Type URI	https://echo.labstack.com/pro/problems/admin-busy
Code	admin_busy
HTTP status	503

HTTP status	English title
503	Service Unavailable

When it occurs

All expensive-view slots are in use, the action receipt cache is full, or your Config.RateLimit callback returned an error.

Client handling

Retry after a short wait. The console sends no Retry-After header for this code.

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_busy",
  "detail": "",
  "status": 503,
  "title": "Service Unavailable",
  "type": "https://echo.labstack.com/pro/problems/admin-busy"
}

Server correction

Set Config.MaxExpensive to the backend’s capacity. Check expensive-view concurrency, action receipt capacity and errors from Config.RateLimit.

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.