Skip to content
Error codes · realuptime errors ingest

RU-4004: Malformed error batch

The batch failed validation and was refused WHOLE: accepting the parsed half of a broken batch would fabricate data. The refused events are counted as dropped_malformed on your dashboard. Ships with `reason: "malformed"`.

On the wire

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

Common causes

  • A hand-rolled client not matching the ingest payload shape.
  • A field with the wrong type (for example a numeric string where a number is required).
  • An empty events array, or a batch over the per-batch event cap.

How to fix it

  1. Read the `error` field: it names the exact failing field.
  2. Use an official SDK, or match its payload shape exactly.
  3. Resend the corrected batch; the refused one wrote nothing.

Still stuck?

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