Skip to content
Error codes · Status pages & incidents

RU-5003: Incident conflicts with live outage state

The request tried to resolve an incident whose component is still measurably down. realuptime refuses to let a status page say "resolved" while its own probes disagree, unless the resolve is explicitly forced.

On the wire

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

Common causes

  • Resolving an incident before the underlying check has actually recovered.
  • Automation resolving on a timer rather than on recovery.

How to fix it

  1. Wait for the check to recover: the incident can then resolve normally.
  2. If you are certain the probe is wrong, pass `force: true` to override; the override is deliberate, never the default.

Related codes

  • RU-5002: Incident not found or not creatable

Still stuck?

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