Skip to main content
Exception Record Notifications alert the relevant team when new failing records are written or when existing records change lifecycle state. They are separate from metric alert notifications — metric alerts fire on the aggregate result (the metric failed), exception notifications fire on the individual records (these specific rows failed).

​
How exception notifications are sent

Exception notifications are sent by an Action. An Action rule starts from a trigger, optionally filters on conditions, and then runs one or more steps. To notify a team about exception records, build a rule with:
  1. Trigger — Exception Created. Fires when a new exception record is written. Add a condition such as Metric equals your metric to limit the rule to one metric.
  2. Step — Send Notification. Choose the Audience, the people or groups who should receive the notification.
A rule can include other steps in the same flow. For example, an Assign Owner step before Send Notification assigns the record and then notifies the audience.
Action rule canvas with the Send Notification step selected and its Audience panel

The Send Notification step: choose who should receive the notification

See Actions for how to build, validate, and save a rule, and for the Execution and Audit tabs that show when a rule ran.

​
Notification channels

Notifications are delivered through the channels you configure under Organization → Integration. Selecting the Notification filter shows the available channels:
  • Email
  • Slack
  • Microsoft Teams
  • Google Chat
Channels page filtered to Notification showing Email, Slack, Microsoft Teams and Google Chat

Organization → Integration → Channels, filtered to Notification

Setup guides: Email, Slack, Microsoft Teams, and Google Chat.
Exception notifications are separate from metric alert notifications. If a metric fails, the metric’s alert notification fires on the aggregate result whether or not an Action exists for its exception records.