Skip to content
Error codes · realuptime errors ingest

RU-4017: Error batch body too large

An events batch's raw request body exceeded the ingest endpoint's byte-size ceiling and was refused whole, before any JSON parsing. This is a coarser, earlier check than RU-4009 (oversize_context): that one catches one map inside an otherwise-reasonable batch, this one catches a body too large to safely parse at all. Ships with `reason: "oversize_body"`.

On the wire

Ships with HTTP status 413, carrying "code": "RU-4017" in the response body alongside the human-readable error message. Existing fields are never replaced by the code: it is additive.

Common causes

  • A batch built by concatenating many events' worth of frames, breadcrumbs, or context without checking the running size.
  • A hand-rolled client streaming an unbounded payload instead of the SDK's own bounded batching.

How to fix it

  1. Use the official SDK, which batches and flushes well under this ceiling.
  2. Split a large batch into several smaller POSTs rather than one giant one.

Related codes

  • RU-4009: Error event context too large

Still stuck?

Ask support and mention RU-4017: the code pins down the exact refusal path, so you skip the diagnostic back-and-forth.