Skip to content

Configure Pipeline Email Alerts

Pipeline alerts let a SchemAlign pipeline notify one or more recipients when important run events occur.

Alert rules belong to a specific pipeline and apply regardless of how that pipeline starts: manually from Workspace, from a schedule, from a File Arrival trigger, through the pipeline API, or from an inbound HTTP trigger.

Open pipeline alerts

  1. Open Workspace.
  2. Select the pipeline you want to monitor.
  3. Choose Alerts from the pipeline toolbar.
  4. Review existing alert rules or choose Add alert.

You need permission to edit the pipeline to create, change, or remove its alert rules.

Choose when to send

An email alert rule can watch one or more pipeline events:

Event When it sends
Run started The worker begins processing the pipeline run.
Run succeeded The run finishes successfully.
Run failed The run reaches a failed terminal state.
Run cancelled The run is cancelled before normal completion.
Run finished Any terminal result: succeeded, failed, or cancelled.

Run finished is an umbrella event

Selecting Run finished replaces the individual succeeded, failed, and cancelled selections for that rule. This prevents duplicate notifications for the same terminal result.

Add recipients

Enter one or more email addresses separated by commas or new lines.

A single rule can contain up to 50 recipients. Duplicate addresses are removed when the rule is normalized.

You can create multiple alert rules for the same pipeline when different teams need different event selections or recipient lists.

Optional execution-log attachment

Enable Attach the execution log when the notification should include SchemAlign's generated run log.

The execution log is the only supported alert attachment. Uploaded files and pipeline-produced artifacts are never attached to alert emails.

Large generated logs may be truncated to the notification attachment limit configured for the SchemAlign instance.

What the email contains

Pipeline alert messages include operational context such as:

  • event result
  • organization
  • project
  • pipeline
  • trigger type and trigger name when available
  • run ID
  • queued, started, and finished times
  • run duration
  • failure details when the run contains an error
  • a link back to the pipeline when the SchemAlign instance has a public application URL configured

For File Arrival runs, the notification can also include the arriving file name and SFTP path. HTTP-triggered runs can include HTTP trigger details such as the trigger slug, method, or request ID when available.

The generated subject format is:

[SchemAlign] {Run result}: {Organization} / {Project} / {Pipeline}

Notification timestamps are rendered in the SchemAlign instance's configured notification display timezone using a 12-hour AM/PM format.

Edit or stop an alert

Open Alerts for the pipeline and select an existing rule to change:

  • events
  • recipients
  • execution-log attachment behavior

To stop a rule from sending notifications, delete the rule. Deleting an alert rule does not affect the pipeline itself and does not change other saved alert rules.

Delivery behavior

Email is the currently available notification channel. Slack and Microsoft Teams are reserved for future channels and are not currently available.

The SchemAlign instance must have email delivery configured. If SMTP delivery is unavailable, Workspace warns that a rule can be saved but messages will not send until email delivery is configured.

Alert delivery is best-effort and is deliberately isolated from pipeline execution:

  • an email delivery failure does not turn a successful pipeline into a failed run
  • the pipeline result remains authoritative
  • notification delivery failures are written to the run log for troubleshooting

SchemAlign sends pipeline alert messages from:

no-reply@schemalign.com

Failures only

Use Run failed for operations teams that only need actionable failure notifications.

All terminal outcomes

Use Run finished when recipients need one message after every pipeline run, regardless of outcome.

Start and finish

Use Run started together with Run finished when a team needs visibility into both run initiation and completion.

Troubleshooting

The rule saves but no email arrives

Check:

  1. whether email delivery is configured for the SchemAlign instance
  2. the recipient address
  3. the pipeline run log for notification delivery failures
  4. the recipient system's junk/quarantine controls

I received more messages than expected

Review the saved rules for the pipeline. Multiple rules can notify overlapping recipient groups.

Within one rule, Run finished replaces the individual succeeded, failed, and cancelled outcomes to avoid terminal-event duplicates.