Skip to content
Error codes · Monitors, checks & agents

RU-3008: Notification channel not found

No notification channel with that ID exists on this account. realuptime deliberately does not distinguish "belongs to another account" from "never existed".

Where it is raised

  • POST /api/v1/notification-channels/{id}/test
  • GET /api/v1/notification-channels/{id}
  • PATCH /api/v1/notification-channels/{id}
  • DELETE /api/v1/notification-channels/{id}
  • Keyed MCP endpoint, channel tools

What triggers it

The id is looked up within the caller's account for the get, update, delete and test routes. A channel in another account answers exactly like a missing one.

Example response

POST /api/v1/notification-channels/{id}/test
HTTP 404

{
  "error": "Notification channel not found.",
  "code": "RU-3008"
}

Common causes

  • The channel was deleted.
  • The ID was copied from another account or mistyped.

How to fix it

  1. List your channels with GET /notification-channels and use an ID from the response.

Related codes