Operation result expired

Identifiers

Field	Value
Type URI	https://echo.labstack.com/pro/problems/operation-result-expired
Code	operation_result_expired
HTTP status	409

HTTP status	English title
409	Conflict

When it occurs

The operation finished, but its stored response passed its retention period. The record and its state may still exist; only the response bytes are gone.

Client handling

The original response cannot be replayed. Use operation_state and operation_ref to learn the outcome, or ask an operator. This answer is not proof that no effect happened. A new key is safe only when safe_new_key is true.

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_result_expired",
  "operation_ref": "AAAAAAAAAAAAAAAAAAAAAAAA",
  "operation_state": "completed",
  "safe_new_key": false,
  "status": 409,
  "title": "Conflict",
  "type": "https://echo.labstack.com/pro/problems/operation-result-expired"
}

Server correction

Provide an authorized application API for looking up the business result. Tell clients the Policy.ResultRetention window (24 hours by default). The retained key prevents rerunning work after the response expires.

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.