Operation not applied

Identifiers

Field	Value
Type URI	https://echo.labstack.com/pro/problems/operation-not-applied
Code	operation_not_applied
HTTP status	409

HTTP status	English title
409	Conflict

When it occurs

The operation failed, and execution holds proof that none of its declared effects were applied. No result is stored for replay.

Client handling

A new operation key is allowed only when safe_new_key is true. When false, do not use a new key. The same key keeps returning this answer.

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": "operation_not_applied",
  "operation_ref": "AAAAAAAAAAAAAAAAAAAAAAAA",
  "operation_state": "failed",
  "safe_new_key": false,
  "status": 409,
  "title": "Conflict",
  "type": "https://echo.labstack.com/pro/problems/operation-not-applied"
}

Server correction

Check that every effect is proven not applied and that no duplicate risk remains. Only safe_new_key: true permits a new operation key.

Response fields

Execution middleware

• type (string, always): The exact type URI above.
• title (string, always): The HTTP status text.
• status (integer, always): The HTTP status of the response.
• code (string, always): The stable code above.
• operation_ref (string, always): An opaque reference to the operation. It is set only after ReplayCheck allows the request, and is empty when no operation was found. Use it to look up the operation; it does not grant access.
• operation_state (string, always): started, uncertain, completed or failed; empty when no operation was found.
• safe_new_key (boolean, always): true only when the client may retry with a new key. It is always false when operation_ref and operation_state are empty.

Headers:

• Cache-Control (always): no-store on every execution problem.

Notes:

• Execution removes any Idempotent-Replayed header from problem responses.

Related behavior

See execution for operation state and replay rules.