Skip to content
Error codes · Monitors, checks & agents

RU-3012: Invalid results query request

A parameter on GET /checks/results (REA-564) failed validation: `from`/`to` missing or not a valid ISO-8601 timestamp, `from` not before `to`, a `check_ids` entry that isn't a UUID, `step` not shaped like 30s/5m/1h/1d or outside its accepted range, an unrecognized `region`, a malformed `cursor`, or a `limit` outside its accepted range. The `error` field names the failing parameter.

On the wire

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

Common causes

  • Omitting from or to, or sending one that Date.parse can't read.
  • from at or after to.
  • A check_ids entry that isn't a UUID, or more ids than the endpoint accepts in one call.
  • A step outside the endpoint's accepted range, or written in a unit other than s/m/h/d.
  • A cursor copied from somewhere other than a previous response's next_cursor.

How to fix it

  1. Read the `error` field for the failing parameter.
  2. Compare the request against the API docs at /docs/api, "GET /checks/results".
  3. Pass cursor exactly as returned in a previous response's next_cursor, never hand-constructed.

Related codes

Still stuck?

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