What does realuptime error RU-5012 mean?

The check named in the request is already a component of this status page, so a second component was not created: the public page would otherwise show the same monitor twice.

How do I fix realuptime error RU-5012?

1. List the page's components with GET /status-pages/:id/components and update or import the existing one.

RU-5012: Check already published on this status page: realuptime error codes

On the wire

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

Common causes

Re-creating a component that already exists instead of importing it.
Two infrastructure-as-code resources naming the same check and page.

How to fix it

List the page's components with GET /status-pages/:id/components and update or import the existing one.

Related codes

RU-5009: Status page or component not found

Still stuck?

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