Admin audit unavailable

Identifiers

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

HTTP status	English title
503	Service Unavailable

When it occurs

The console could not write the action’s intent record to the audit sink, so it did not run the action. This happens when Config.Audit is nil and AllowUnauditedWrites is false, or when the sink returns an error.

Client handling

No change was made. Retry later with the same action_id and input.

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

Server correction

Fix the audit sink so it accepts intent records. Check capacity, permissions and the recording deadline. No mutation ran for this attempt.

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.