Skip to content
Error codes · Monitors, checks & agents

RU-3009: Duplicate notification channel name

The account already has a notification channel with that name. Names are unique per account so alert rules can refer to them unambiguously.

Where it is raised

  • POST /api/v1/notification-channels
  • Keyed MCP endpoint, channel create tool

What triggers it

The formatter's refusal text for a name already held by the account is matched exactly and sent as a 409. The comparison is within the account, so another account's channel of the same name is no conflict.

Example response

POST /api/v1/notification-channels
HTTP 409

{
  "error": "You already have a channel with that name.",
  "code": "RU-3009"
}

Common causes

  • Re-creating a channel that already exists instead of updating it.

How to fix it

  1. Choose a different name, or update the existing channel with PATCH /notification-channels/:id.

Related codes