Admin timeout
Identifiers
Section titled “Identifiers”| Field | Value |
|---|---|
| Type URI | https://echo.labstack.com/pro/problems/admin-timeout |
| Code | admin_timeout |
| HTTP status | 504 |
| HTTP status | English title |
|---|---|
| 504 | Gateway Timeout |
When it occurs
Section titled “When it occurs”A panel callback timed out or the request was canceled. Config.Timeout covers the entire request, including middleware. It defaults to ten seconds and accepts one millisecond through one minute.
Client handling
Section titled “Client handling”Retry later, or narrow the request, for example with a smaller limit or a shorter period.
Example response
Section titled “Example response”If your application installs a custom handler, the body may differ.
HTTP/1.1 504 Gateway TimeoutContent-Type: application/problem+jsonCache-Control: no-store
{ "code": "admin_timeout", "detail": "", "status": 504, "title": "Gateway Timeout", "type": "https://echo.labstack.com/pro/problems/admin-timeout"}Server correction
Section titled “Server correction”Check backend latency. Limit expensive reads by time range or page size. After a mutation timeout, inspect target state before starting another action.
Response fields
Section titled “Response fields”Admin console
Section titled “Admin console”code(string, always): The stable code above.detail(string, always): The console always sendsdetail. 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 asConflict, 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_foundwith an emptydetail.
Related behavior
Section titled “Related behavior”See the admin console for access checks, action IDs and audit failures.