Skip to main content

Notifications

Configure email notifications to receive alerts when production lines succeed or fail.

Overview​

Notifications send email alerts based on production line execution outcomes. Configure notifications at different levels depending on how broadly you want to receive alerts:

  • Solution level: Receive alerts for all production lines in the solution
  • Production line level: Receive alerts for a specific production line
  • Task level: Receive alerts for individual task outcomes

Notification Types​

TypeWhen SentUse Case
On SuccessProduction line completes successfullyConfirm critical pipelines completed
On FailureProduction line failsAlert teams to investigate issues

Configuring Notifications​

The notification setup process is the same at every level. The only difference is the scope of what triggers the notification.

Add a new notification​

  1. Open the solution, production line or task panel
  2. Make sure you're viewing the Properties tab
  3. Scroll to the Notifications section
  4. Enter or select an email address
  5. Select a notification type (On Success or On Failure)
  6. Click Add Notification

Notifications form

  • Use solution-level notifications when you want alerts for all production lines within a solution
  • Use production line-level notifications when you want alerts for a specific pipeline
  • Use task-level notifications when you need alerts for specific operations within a production line

Managing Notifications​

To remove a notification:

  1. Open the properties panel for the solution, production line, or task
  2. Find the notification in the Notifications section
  3. Click the delete icon next to the notification

Best Practices​

Start broad, then refine: Configure solution-level failure notifications first. Add task-level notifications only for critical operations that need immediate attention.

Use failure notifications for monitoring: On Failure notifications are more actionable than On Success. Focus on alerting when something goes wrong rather than confirming every successful run.

Avoid notification fatigue: Too many notifications reduce their effectiveness. Reserve notifications for pipelines that require human attention when they fail.

Consider your team structure: Use distribution lists or team email addresses rather than individual emails. This ensures notifications reach the right people even when team members are unavailable.