Admin reason required

Identifiers

Field	Value
Type URI	https://echo.labstack.com/pro/problems/admin-reason-required
Code	admin_reason_required
HTTP status	422

HTTP status	English title
422	Unprocessable Entity

When it occurs

The action requires a reason, and the commit did not include one.

Client handling

Enter a non-empty reason and submit again.

Example response

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

HTTP/1.1 422 Unprocessable Entity
Content-Type: application/problem+json
Cache-Control: no-store

{
  "code": "admin_reason_required",
  "detail": "",
  "status": 422,
  "title": "Unprocessable Entity",
  "type": "https://echo.labstack.com/pro/problems/admin-reason-required"
}

Server correction

Check that the action form includes its required reason. Keep credentials and secrets out of that reason.

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.