Skip to content
Error codes · realuptime errors ingest

RU-4009: Error event context too large

One event in the batch carried more tags, context entries, or frame local variables than the hard limit allows, so the batch was refused WHOLE and counted as a malformed drop. This is not the ordinary size cap: going a little over a cap truncates and tells you how many entries were dropped, on the issue itself. This code means a map arrived with hundreds of entries, which is a bug in the code building the event rather than an over-eager integration. Ships with `reason: "oversize_context"`.

On the wire

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

Common causes

  • A whole request body, response, or ORM object passed to setContext instead of a few named values.
  • Tags set in a loop, one per record, instead of one tag naming the batch.
  • Local-variable capture switched on in a function holding a very large frame.

How to fix it

  1. Set a handful of named tags and context entries, not a dump of an object.
  2. Move bulk data out of context: an error tracker stores what identifies the failure, not the payload that caused it.
  3. Ordinary overage needs no action; the issue detail states how many entries a size cap dropped.

Related codes

Still stuck?

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