Admin action ID reused
Identifiers
Section titled “Identifiers”| Field | Value |
|---|---|
| Type URI | https://echo.labstack.com/pro/problems/admin-action-id-reused |
| Code | admin_action_id_reused |
| HTTP status | 409 |
| HTTP status | English title |
|---|---|
| 409 | Conflict |
When it occurs
Section titled “When it occurs”The console refused an action commit. The confirmation token is missing, malformed or invalid for this action and input; the receipt cache holds different input under this action_id; or the audit sink already has this action ID with different content.
Client handling
Section titled “Client handling”When the confirmation does not verify, request a new preview and commit with the confirmation it returns. Do not reuse an action_id for different input. To retry the same action, resend the identical input with the same action_id and confirmation. For a new action, open a fresh form, which generates a new action_id.
Example response
Section titled “Example response”If your application installs a custom handler, the body may differ.
HTTP/1.1 409 ConflictContent-Type: application/problem+jsonCache-Control: no-store
{ "code": "admin_action_id_reused", "detail": "", "status": 409, "title": "Conflict", "type": "https://echo.labstack.com/pro/problems/admin-action-id-reused"}Server correction
Section titled “Server correction”Check that action forms preserve their action_id, confirmation and input across retries. A different action needs a new preview. A lost response must not generate a new action ID.
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.