Admin in progress

Identifiers

Field	Value
Type URI	https://echo.labstack.com/pro/problems/admin-in-progress
Code	admin_in_progress
HTTP status	409

HTTP status	English title
409	Conflict

When it occurs

The same action, with the same action_id and input, is still running in this console.

Client handling

Wait, then resend the same request with the same action_id to receive its receipt. Do not create a new action_id: that would request the change a second time.

Example response

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

HTTP/1.1 409 Conflict
Content-Type: application/problem+json
Cache-Control: no-store

{
  "code": "admin_in_progress",
  "detail": "",
  "status": 409,
  "title": "Conflict",
  "type": "https://echo.labstack.com/pro/problems/admin-in-progress"
}

Server correction

Check the running action and reload its target if the response was lost. A new action ID can apply the change a second time.

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.