Skip to content

docs(TSP-1444): document alarm notification channel failure visibility #816

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
claude wants to merge 1 commit into from
+20 −0
Closed

docs(TSP-1444): document alarm notification channel failure visibility #816

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 20 additions & 0 deletions build/agents/build-your-agent/alerts.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -66,6 +66,10 @@

For Slack setup details, see [Slack integration](/integrations/popular-integrations/slack). For Teams, see [Microsoft Teams integration](/integrations/popular-integrations/microsoft-teams).

<Note>
When you remove a connected OAuth account (Slack or Teams), a confirmation dialog shows how many alert rules route notifications through that account. Review those rules before disconnecting to avoid breaking alert delivery.
</Note>

### Setting up an alert rule

1. Navigate to your agent and open the **Alerts** tab
Expand All @@ -78,6 +82,22 @@

You can create multiple alert rules, each with different triggers and channels. Existing rules appear as cards showing the trigger description, active channels, and controls to edit, delete, or toggle them on/off.

### Notification channel health

When a notification channel experiences a permanent delivery failure — such as a deleted OAuth account, a removed Slack bot, an archived channel, or a token that can no longer be renewed — Relevance AI surfaces warnings so you can identify and fix the issue before critical notifications are missed.

#### Channel issue badge

Alert rule cards display a yellow **Channel issue** badge when the rule's notification channel has a permanent delivery failure. The badge appears in both the agent and eval views, making broken channels easy to spot at a glance.

Check warning on line 91 in build/agents/build-your-agent/alerts.mdx

View check run for this annotation

Mintlify / Mintlify Validation (relevanceai) - vale-spellcheck

build/agents/build-your-agent/alerts.mdx#L91 

Did you really mean 'eval'?

#### Warning banner when editing

When you open an alert rule with a broken channel for editing, a warning banner appears in the channel configuration step. The banner identifies which specific channel is broken and explains why delivery failed, so you know exactly what needs to be updated.

#### Fallback-to-email delivery

If all of an alert rule's configured notification channels are permanently broken, Relevance AI automatically falls back to emailing the alert rule's original creator. This ensures critical notifications are still delivered even when all configured channels fail.

---

## Agent escalations
Expand Down
Loading