Skip to content
deedglassdocs

response_too_large

The service’s answer passed the connector’s maxresponsebytes (4 MiB by default, 16 MiB at most), counted after decompression.

HTTP 502 · api_error · not retryable

What happened

Section titled “What happened”

The service’s answer passed the connector’s max_response_bytes (4 MiB by default, 16 MiB at most), counted after decompression. Deedglass read at most one byte past the limit and kept none of it. The call ran, so the action’s outcome is unknown and its witness verdict UNVERIFIABLE.

What to do

Section titled “What to do”

Narrow the request (a page size, a filter), or raise max_response_bytes.

Example

Section titled “Example”
HTTP 502 · response_too_large
{
  "error": {
    "type": "api_error",
    "code": "response_too_large",
    "message": "The service answered with more than the connector's max_response_bytes, so Deedglass kept none of it. The call ran.",
    "param": null,
    "request_id": "req_01j9zr3m5k8q2w7x4t6v0b1c9d",
    "doc_url": "https://docs.deedglass.com/errors/response_too_large"
  }
}

The message is for a person and can get more exact over time: branch on type and code, never on the message.

In the SDKs

Section titled “In the SDKs”
SDK Raised as
TypeScript (@deedglass/sdk) APIError with code === "response_too_large"
Python (deedglass) deedglass.APIError with .code == "response_too_large"
Section titled “Related”