Alerts

Notify a channel when a run reaches an outcome.

An Alert is the outbound half of run handling: when a run reaches some outcome, the alert notifies a channel — a Teams card, a Slack message, an email, a webhook, and so on. It is the opposite of a Trigger, which is inbound — an event that starts a run. The two are never the same thing.

Alerts are managed on the Alerts page (formerly Events). The channels they notify are ordinary Alert-capable Connections — there is no separate "Event Connections" page anymore; an alert channel is just a connection with the Alert capability (see Connections).

What an alert ties together

An alert picks:

• one or more reasons — when it fires;
• one channel — the Alert-capable connection the notification goes to;
• the message body / per-field values for that channel, which may embed placeholder variables resolved at fire time.

Reasons — when an alert fires

• On failure — a run ended with status failed.
• On success — a run ended with status succeeded.
• On cancellation — a run was cancelled by an operator.
• Rows ≥ threshold — the rows-written count crossed a configured number.
• Duration ≥ threshold — the run took longer than a configured wall-clock budget.

The Alerts list can be filtered by reason and by channel, alongside the name search.

Channels

The channel is any connection with the Alert capability. The common ones are Microsoft Teams, Slack, Webex, Email (SMTP), Microsoft 365 Mail, Azure Logic Apps, Azure DevOps, Azure Event Grid, and a generic Webhook. One connection can serve several roles — a Kafka connection, for instance, can be a sink, a trigger, and an alert channel. See the Connector Catalogue for each channel's configuration.

You select the channel in the alert editor; the editor then shows the fields that channel expects (card body, mail recipients, request body, …).

Placeholder variables

Field values can embed system variables that are substituted when the alert fires, so one alert can describe many transports. Examples include {{transport.name}}, {{transport.dataObject}}, and {{client.name}}. The alert editor offers a picker for the full set of available variables.

Roles

Creating and editing alerts requires the Admin role. Read-only users can see them but not change them. See Authentication & Roles.