Skip to content
Error codes · Monitors, checks & agents

RU-3004: Invalid response assertions

The response assertions on this check are not internally consistent (for example a body operator without a value, a status range whose minimum exceeds its maximum, or a JSON assertion whose path and condition do not pair up), or assertions were set on a non-HTTP check.

On the wire

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

Common causes

  • An assertion operator supplied without its value, or vice versa.
  • A status range like 500–200.
  • A JSON path with no condition, an "exists" condition given a value it does not take, or an "equals"/"contains" condition with no value.
  • A JSON path using a wildcard, a filter expression, or recursive descent, none of which are supported.
  • Setting response assertions on a TCP, SMTP, or heartbeat check.

How to fix it

  1. Pair every assertion operator with a value.
  2. Keep status ranges min ≤ max.
  3. Write JSON paths as plain keys and indexes, for example data.items[0].status.
  4. Only set response assertions on http checks.

Related codes

Still stuck?

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