Skip to main content
Notifications tell you when runs fail, when thresholds breach, or when someone assigns you work in the product. You choose channels and categories so urgent signals reach you without noise.

​
Channels

Digest or immediate mail to your verified address. Respect your org’s allowlists so messages are not quarantined.

​
Event categories

Typical toggles include:
  • Pipeline run – success, failure, cancellation, duration SLA miss
  • Reverse ETL sync – batch completion, DLQ growth, credential expiry warnings
  • Governance – contract violations, catalog harvest failures
  • Security – new API key created, SSO certificate nearing expiry (admin-only)
You can subscribe to all failures or limit to pipelines you own or watch.

​
Quiet hours and routing

Set quiet hours with a fallback channel (for example, page only the on-call integration) so overnight failures still surface. Some teams route dev notifications to a low-priority channel and prod to PagerDuty.
Alert rules defined in Observability reference these defaults; individual rules can override recipients for specific pipelines.

​
Testing delivery

Use Send test notification on each channel to confirm spam filters and mobile settings. Fix bounces before you rely on email for production incidents.

Alerts

Define when notifications fire.

Teams and permissions

Who can change org-wide notification routes.