This guide explains how registered users can configure pipeline notifications to receive alerts for specific pipeline run outcomes. You can subscribe to two types of notification: completion alerts for Success, Failure, Cancelled, and Skipped runs, and anomaly alerts for pipeline runs whose duration deviates significantly from historical baselines. Both notification types are available within the projects and environments you have access to. Notifications are sent only for scheduled or API-driven pipeline runs—pipelines run manually through don’t generate notifications. These alerts help you respond quickly to issues, minimize downtime, and improve overall reliability.
Notifications can be delivered via:
Use cases
- Environment-specific routing: Send development failures to a sandbox channel and production alerts to your high-priority alerts channel.
- Noise reduction: Rather than building alerts into every pipeline, simply subscribe to a project or environment once.
- Anomaly detection: Receive alerts when a pipeline run takes significantly longer or shorter than expected, so you can investigate performance issues before they escalate.
Prerequisites
Before setting up pipeline notifications, ensure the following:
- You have a registered account.
- You have access to the relevant projects and environments where the data pipelines are running.
- If you plan to use Slack notifications, you have access to a Slack workspace and a configured Slack webhook URL.
Pipeline completion alerts
Select a delivery method to set up completion alerts:
When you select Email as the delivery method for a pipeline notification, alerts are sent to the email address associated with your account.No additional setup is required. Once you select Email, alerts are delivered automatically when your chosen trigger conditions are met.
- In the left navigation, click your Profile & Account icon. Then, select Notifications from the menu.
- Click Add notification at the top.
- In the Add notification dialog, select the Project and Environment you’d like to be notified about.
- Under Pipeline completion alerts, click Add, then select the trigger types you want to subscribe to: Success, Failure, Cancelled, and/or Skipped.
- Under How do you want to receive this notification?, select Email.
- Click Add notification.
When you select Slack as the delivery method for a pipeline notification, alerts are sent to a Slack channel of your choice via an incoming webhook URL.Prerequisites
Before setting up Slack notifications, you must create a Slack app and generate an incoming webhook URL in your Slack workspace. For step-by-step instructions, see Sending messages using incoming webhooks.Setup
When configuring a pipeline notification with Slack as the delivery method, provide the following:The incoming webhook URL generated in your Slack workspace.
A descriptive name for this webhook, used to identify it on the Notifications page.
- In the left navigation, click your Profile & Account icon. Then, select Notifications from the menu.
- Click Add notification at the top.
- In the Add notification dialog, select the Project and Environment you’d like to be notified about.
- Under Pipeline completion alerts, click Add, then select the trigger types you want to subscribe to: Success, Failure, Cancelled, and/or Skipped.
- Under How do you want to receive this notification?, select Slack.
- Enter a Slack Webhook URL and a Slack Webhook Name.
- Click Add notification.
When you select Webhook as the delivery method for a pipeline notification, alerts are sent as HTTP POST requests to an endpoint of your choice. You can also supply a custom JSON payload template to control exactly what data is sent.Webhook notifications are outbound only. can’t receive incoming webhook data or use webhooks to trigger pipeline runs. Outbound payloads aren’t signed with HMAC, so receiving endpoints can’t use HMAC to verify the request.
Setup
When configuring a pipeline notification with Webhook as the delivery method, provide the following:The endpoint that receives the notification.
A descriptive name for this webhook, used to identify it on the Notifications page.
A custom JSON template using ${variableName} syntax to control the notification body. For example: {"text": "Pipeline ${pipelineName} status ${status}"}. Click View available variables to see the full list of supported variables.
- In the left navigation, click your Profile & Account icon. Then, select Notifications from the menu.
- Click Add notification at the top.
- In the Add notification dialog, select the Project and Environment you’d like to be notified about.
- Under Pipeline completion alerts, click Add, then select the trigger types you want to subscribe to: Success, Failure, Cancelled, and/or Skipped.
- Under How do you want to receive this notification?, select Webhook.
- Enter a Webhook URL, a Webhook Name, and a Payload Template.
- Click Add notification.
Available variables
The following variables are available for use in the payload template. Select the ones that best fit your needs.| Variable | Description |
|---|
${pipelineName} | Pipeline name |
${status} | Execution status |
${finishedAt} | Completion timestamp |
${pipelineExecutionId} | Execution ID |
${projectId} | Project ID |
${accountId} | Account ID |
Example payload
The following example uses all available variables in a realistic payload structure:{
"text": "Pipeline ${pipelineName} finished with status ${status}",
"pipeline": {
"name": "${pipelineName}",
"status": "${status}",
"executionId": "${pipelineExecutionId}",
"finishedAt": "${finishedAt}"
},
"context": {
"projectId": "${projectId}",
"accountId": "${accountId}"
}
}
What the completion alert includes
Each completion alert includes the following details about the pipeline run:
- Project name
- Environment name
- Pipeline name
- End time of the pipeline run
It also includes a View Pipeline Run Details link to the Pipeline run history and an Update Notification Settings link to the Notifications page.
Anomaly alerts
Anomaly alerts notify you when a pipeline run’s duration deviates significantly from its historical baseline.
To receive anomaly alerts, keep the following requirements in mind:
- Minimum run requirement: A pipeline must have at least 10 successful runs before the system can generate anomaly alerts.
- Impact of new versions: Baselines are tied to specific publication versions. When you publish a new pipeline version, the baseline resets. The new version must complete 10 successful runs before alerts resume.
Duration anomalies
compares every pipeline run’s duration against that pipeline’s own recent history. If the run falls well outside the range of normal durations, it’s flagged as a duration anomaly.
There are two types of duration anomaly:
- Slow anomaly—the run took longer than expected. This can be detected while the pipeline is still running, as well as at completion.
- Fast anomaly—the run finished unusually quickly. This is only detected at completion.
How the expected range is calculated
uses up to the most recent 300 successful runs of a pipeline to establish its baseline. A minimum of 10 successful runs is required—pipelines with fewer runs in their history don’t generate anomaly alerts.
From those durations, builds an expected range around the pipeline’s typical duration:
- It takes the median (middle) run duration as the center of “normal.”
- It measures how far normal runs spread above the median—out to the slowest runs that are still routine (the 99th percentile). It does the same on the fast side, down to the quickest routine runs (the 1st percentile).
- The upper bound (slow threshold) is the median plus twice that upward spread. A run has to land well beyond even the normally-slow end of the range before it’s flagged as slow.
- The lower bound (fast threshold) is the median minus twice the downward spread, and never drops below zero. For most pipelines it works out to zero—so they’re never flagged as “too fast.” It only becomes meaningful for pipelines that normally run long and consistently, where finishing in a fraction of the usual time is a genuine signal that the run did little or no work.
always applies a small minimum spread, so a pipeline that finishes in almost exactly the same time every run still gets a sensible margin instead of a hair-trigger threshold.
In plain terms: the range scales to how variable each pipeline normally is. Steady pipelines get a tight range, so even a modest slowdown is flagged; naturally variable pipelines—or ones with a mix of quick and long runs—get a wider range, so ordinary fluctuation doesn’t trigger false alerts.
Subscribe to anomaly alerts
Select a delivery method to set up anomaly alerts:
When you select Email as the delivery method for an anomaly alert, notifications are sent to the email address associated with your account.No additional setup is required. Once you select Email, alerts are delivered automatically when an anomaly is detected.
- In the left navigation, click your Profile & Account icon. Then, select Notifications from the menu.
- Under Anomaly alerts, click Add.
- Select Enable anomaly alerts.
- Under How do you want to receive this notification?, select Email.
- Click Add notification.
When you select Slack as the delivery method for an anomaly alert, notifications are sent to a Slack channel of your choice via an incoming webhook URL.Prerequisites
Before setting up Slack notifications, you must create a Slack app and generate an incoming webhook URL in your Slack workspace. For step-by-step instructions, see Sending messages using incoming webhooks.Setup
When configuring an anomaly alert with Slack as the delivery method, provide the following:The incoming webhook URL generated in your Slack workspace.
A descriptive name for this webhook, used to identify it on the Notifications page.
- In the left navigation, click your Profile & Account icon. Then, select Notifications from the menu.
- Under Anomaly alerts, click Add.
- Select Enable anomaly alerts.
- Under How do you want to receive this notification?, select Slack.
- Enter a Slack Webhook URL and a Slack Webhook Name.
- Click Add notification.
When you select Webhook as the delivery method for an anomaly alert, notifications are sent as HTTP POST requests to an endpoint of your choice. You can also supply a custom JSON payload template to control exactly what data is sent.Webhook notifications are outbound only. can’t receive incoming webhook data or use webhooks to trigger pipeline runs. Outbound payloads aren’t signed with HMAC, so receiving endpoints can’t use HMAC to verify the request.
Setup
When configuring an anomaly alert with Webhook as the delivery method, provide the following:The endpoint that receives the notification.
A descriptive name for this webhook, used to identify it on the Notifications page.
A custom JSON template using ${variableName} syntax to control the notification body. For example: {"text": "Pipeline ${pipelineName} status ${status}"}. Click View available variables to see the full list of supported variables.
- In the left navigation, click your Profile & Account icon. Then, select Notifications from the menu.
- Under Anomaly alerts, click Add.
- Select Enable anomaly alerts.
- Under How do you want to receive this notification?, select Webhook.
- Enter a Webhook URL, a Webhook Name, and a Payload Template.
- Click Add notification.
Available variables
The following variables are available for use in the payload template. Select the ones that best fit your needs.| Variable | Description |
|---|
${pipelineName} | Pipeline name |
${environmentDisplayName} | Environment display name |
${status} | Pipeline status |
${startedAt} | Execution start timestamp |
${elapsedDurationSeconds} | Elapsed duration in seconds |
${expectedUpperBoundSeconds} | Expected upper bound in seconds |
${expectedLowerBoundSeconds} | Expected lower bound in seconds |
${pipelineExecutionId} | Execution ID |
${triggerType} | Pipeline trigger type |
${projectId} | Project ID |
${accountId} | Account ID |
Example payload
The following example uses all available variables in a realistic payload structure:{
"text": "Pipeline ${pipelineName} has a duration anomaly elapsed ${elapsedDurationSeconds}s exceeds expected upper bound of ${expectedUpperBoundSeconds}s",
"pipeline": {
"name": "${pipelineName}",
"environment": "${environmentDisplayName}",
"executionId": "${pipelineExecutionId}",
"triggerType": "${triggerType}",
"startedAt": "${startedAt}"
},
"anomaly": {
"elapsedDurationSeconds": "${elapsedDurationSeconds}",
"expectedUpperBoundSeconds": "${expectedUpperBoundSeconds}",
"expectedLowerBoundSeconds": "${expectedLowerBoundSeconds}"
},
"context": {
"projectId": "${projectId}",
"accountId": "${accountId}"
}
}
What the anomaly alert includes
Anomaly alerts include the following details:
- Pipeline name
- Anomaly type
- Environment name
- Start timestamp
- Elapsed duration
- Expected upper and lower bounds
It also includes a View Pipeline Run Details link to the Pipeline run history and an Update Notification Settings link to the Notifications page.
Managing pipeline notifications
After creating a notification, you’ll return to the Notifications page, where your pipeline notification has been added, displaying the following:
- Project name
- Environment name
- Type — the notification type: Completion or Anomaly
- Trigger — the trigger types you selected
- Delivery — the delivery method or methods you selected, with the webhook or Slack name shown in parentheses where applicable
You can select more than one delivery method for a single notification.
If you change your mind, you can cancel the deletion action by clicking Cancel in the confirmation dialog.
