Skip to main content
Hatchet monitors your task runs and sends alerts when tasks fail persistently. Alerts fire after all retries are exhausted and can be delivered to Slack channels or email addresses. All alerting is configured in the Hatchet dashboard — no code changes are required.
Alerting is configured entirely through the Hatchet dashboard. There are no SDK methods or environment variables required to enable it.

Alert conditions

Hatchet sends an alert when:
  • A task fails after exhausting all configured retries
  • Failures recur within an adjustable alerting window
Alerts are rate-limited by the alerting window to avoid flooding your channel with repeated notifications for the same issue.

Setting up Slack alerts

1

Open notification settings

In the Hatchet dashboard, navigate to SettingsNotifications.
2

Connect your Slack workspace

Click Connect Slack. You will be redirected to Slack’s OAuth flow. Grant Hatchet permission to post to your workspace.
3

Select a channel

After authorizing, choose the Slack channel where alerts should be posted.
4

Save and test

Click Save. Use the Send test alert button to verify that the message arrives in your channel.

Setting up email alerts

1

Open notification settings

In the Hatchet dashboard, navigate to SettingsNotifications.
2

Add an email address

Enter one or more email addresses in the Email alerts field.
3

Save

Click Save. Hatchet will send a confirmation to each address before enabling alerts.

Alerting window

The alerting window controls how frequently Hatchet will send alerts for the same recurring failure. For example, if a cron task fails every minute and your window is 30 minutes, you will receive one alert rather than sixty. You can adjust the alerting window from the Notifications settings page. Shorter windows give you faster feedback; longer windows reduce noise for tasks that are retried frequently.

Managing alerts

All notification channels and their status are listed on the SettingsNotifications page. From there you can:
  • Enable or disable individual channels without deleting them
  • Update the Slack channel or email addresses
  • Adjust the alerting window
  • Send a test alert to confirm delivery
Alerts reference the tenant they belong to, so notifications from different tenants are kept separate even if they share the same Slack workspace.

Next steps

Dashboard

View run history and inspect failures directly in the dashboard.

Task logs

Correlate alerts with the logs captured during a failed run.

Build docs developers (and LLMs) love