Skip to content
Error codes · Monitors, checks & agents

RU-3010: Latency threshold out of range

The requested per-check latency threshold ("degraded above X ms", REA-359) is outside the accepted [1, 10000]ms range. realuptime refuses this explicitly rather than clamping it, so the stored threshold always matches what was actually requested.

On the wire

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

Common causes

  • latencyThresholdMs is 0 or negative.
  • latencyThresholdMs is above 10000 -- at or above the probe's own default timeout, a threshold that high could never fire.
  • latencyThresholdMs is not a finite number (NaN, Infinity, or a non-numeric string).

How to fix it

  1. Use a value between 1 and 10000 milliseconds, or omit the field / send null for no threshold.

Related codes

Still stuck?

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