Notifications

Create notification rules on the project's Notifications page. Each rule has a name, Active or Inactive status, event subscriptions, and delivery targets. Only Active, non-deleted rules send notifications.

Targets

A rule can deliver to Email, Slack, or both. Email accepts 1–20 addresses. Slack requires an HTTPS incoming webhook URL from hooks.slack.com or hooks.slack-gov.com with a /services/ path. See Notification integrations for setup.

Events

The current form groups events into:

• Run started / Run completed: Includes start and result updates for background Runs, with both Passed and Failed results.
• New issue / Issue resolved: Select one or more Issue priorities to include.

There is no current failed-only Run or Run-priority filter. Legacy separately stored event settings are normalized into these grouped subscriptions.

Run started is sent when a case first moves its parent Run to Running. Completed notifications follow the stored test result and can arrive while video is still Processing. The agent's Live View case execution does not use background Run notifications.

New Issue notifications include newly saved findings and reopened Issues. Matching a new occurrence to an existing open Issue does not send another New Issue event. Resolving with a reason sends an Issue resolved event. A deployment webhook's message can appear as Run notification context.

Rule design

Use project-specific rules and team-owned destinations so the people responsible for a workflow can review its results. Restrict Issue priorities where useful, and disable rules temporarily when delivery is not needed.