Operation response too large

Identifiers

Field	Value
Type URI	https://echo.labstack.com/pro/problems/operation-response-too-large
Code	operation_response_too_large
HTTP status	500

HTTP status	English title
500	Internal Server Error

When it occurs

The handler ran, but its response exceeded MaxResponseBytes or could not be buffered. The default limit is 1 MiB. Execution could neither store nor return the response. A business effect may already have happened.

Client handling

Do not repeat the operation automatically. Give operation_ref to an operator, who can find out whether the operation applied. 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 500 Internal Server Error
Content-Type: application/problem+json
Cache-Control: no-store

{
  "code": "operation_response_too_large",
  "operation_ref": "AAAAAAAAAAAAAAAAAAAAAAAA",
  "operation_state": "failed",
  "safe_new_key": false,
  "status": 500,
  "title": "Internal Server Error",
  "type": "https://echo.labstack.com/pro/problems/operation-response-too-large"
}

Server correction

Keep the handler’s response under MaxResponseBytes. Check it together with the journal’s MaxResultBytes. An oversized response does not prove the effect did not happen.

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.