Skip to content
Recuro Docs

Setting Up Alerts

This guide walks you through configuring alerts so you are notified when crons or jobs fail.

Step 1: Configure your notification channel

  1. Go to Settings > Notifications
  2. Choose your alert channel:
    • Email — Alerts are emailed to all team members
    • Slack — Alerts are posted to a Slack webhook URL
    • Discord — Alerts are posted to a Discord webhook URL
  3. For Slack or Discord, paste your incoming webhook URL
  4. Click Save
  5. Optionally, click Test to send a test notification

Getting a Slack webhook URL

  1. Go to api.slack.com/apps and create a new app (or use an existing one)
  2. Enable Incoming Webhooks
  3. Click Add New Webhook to Workspace and select the channel
  4. Copy the webhook URL

Getting a Discord webhook URL

  1. Open your Discord server settings
  2. Go to Integrations > Webhooks
  3. Click New Webhook, select the channel, and copy the URL

Step 2: Enable alerts on your crons

When creating or editing a cron, set the Alert Threshold:

ThresholdBehavior
1Alert after the first consecutive failure
2Alert after 2 consecutive failures
3Alert after 3 consecutive failures

Via the API:

Terminal window
curl -X POST https://app.recurohq.com/api/crons \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Health Check",
    "url": "https://api.yourapp.com/health",
    "method": "GET",
    "cron_expression": "*/5 * * * *",
    "alert_threshold": 2
  }'

With this configuration:

  • First failure: a warning alert is created (visible in the dashboard)
  • Second consecutive failure: a failure alert is sent to your notification channel
  • Next success: a recovery alert is sent

Step 3: Enable alerts on your queues

  1. Go to Queues > [queue] > Edit
  2. Toggle Alerts Enabled on
  3. Save

When alerts are enabled on a queue:

  • A warning alert is created when a job first fails
  • A failure alert is sent when a job exhausts all retries and is dead-lettered

Suppressing alerts during maintenance

If you have planned downtime, create a maintenance window to suppress alerts:

  1. Go to Maintenance Windows
  2. Click New Maintenance Window
  3. Select the resource to suppress (a specific cron, a specific queue, or leave blank for all)
  4. Set the start and end time
  5. Optionally add a reason
  6. Click Create

Alerts for the specified resource are suppressed during the window.

Managing alerts

From the Alerts page:

  • Filter by alert type (failure, warning, recovery, limit_warning) or failure reason
  • Mark as read to dismiss individual alerts
  • Mark all as read to clear the list
  • Delete alerts you no longer need

Next steps