Skip to content
Back to Docs

Alerts & Notifications

Get notified when jobs fail, connections break, or syncs stall.

Overview

SnowPipe can send email alerts for pipeline failures, connection errors, and other events. Alerts are configured per-user and apply across all your pipelines in the current workspace.

Alerts are disabled by default. Enable them from Settings → Alerts in the dashboard.

Enabling Alerts

1

Open alert settings

Navigate to Settings → Alerts in the sidebar.

2

Turn on the master toggle

Flip the Enable Alerts switch at the top. This reveals the full configuration panel.

3

Configure channels, triggers, and throttling

Set up your email addresses, choose which events to alert on, and configure throttle limits. Click Save when done.

Email Channel

Email is the primary alert channel. You can add up to 5 email addresses that will receive alert notifications.

Adding Addresses

Type an email address and click Add. You can add up to 5 addresses. Remove an address by clicking the × button next to it.

Test Email

Click Send Test next to any address to send a test alert. This verifies that the email is delivered correctly and shows up in your alert history.

Enable / Disable

Toggle the email channel on or off independently of the master alert switch. When disabled, no emails are sent even if alerts are enabled.

Triggers

Choose which events should fire an alert. Each trigger can be enabled or disabled independently.

Job Failed

Enabled

Send an alert whenever a pipeline job fails.

Consecutive Failures

Enabled (threshold: 3)

Send an alert when a pipeline fails N times in a row. Configurable threshold (default: 3).

Connection Error

Enabled

Send an alert when a connection test fails or a source/destination becomes unreachable.

Rate Limit Exceeded

Enabled

Send an alert when a source API returns rate limiting errors.

Sync Stalled

Enabled (60 min)

Send an alert when a job has been running longer than the configured threshold. Configurable in minutes (default: 60).

Throttling

Throttling prevents alert fatigue by limiting how many alerts you receive in a given time window.

SettingDefaultRange
Max alerts per hour101 – 100
Cooldown (minutes)51 – 60

When the max alerts per hour is reached, additional alerts are suppressed until the hour window resets. The cooldown prevents duplicate alerts from the same pipeline within the specified window.

Alert History

The History tab on the Alerts settings page shows a log of all sent alerts. Each entry includes:

  • Alert type (job_failed, connection_error, etc.)
  • Channel (email)
  • Timestamp
  • Delivery status (success or error with details)

Statistics cards at the top show totals for the last 24 hours and breakdowns by type and channel for the last 7 days.

Coming Soon

Slack Notifications

Send alerts to Slack channels via incoming webhooks. Configure per-channel routing for different alert types.

Custom Webhook Channel

Send alert payloads to user-defined HTTP endpoints for custom integrations (PagerDuty, Opsgenie, etc.).

Need help?

Reach out at support@snowforge.dev