Docs / Notifications / Troubleshoot Missed Notifications

Troubleshoot Missed Notifications

Published · Last updated: May 2026 · 3 min read

Who this is for

Anyone who expected to receive a notification for an event (alert, backup, deployment) but did not receive it.

What you will complete

Diagnose why a notification was missed and fix the underlying cause.

Step 1: Confirm the event actually occurred

Before troubleshooting notification delivery, confirm the underlying event actually fired.

  • For alerts: go to Alerts → Events and check if the alert event appears in the log.
  • For backups: go to Backups and check the backup history.
  • For deployments: go to the site or app and check the deployment history.

If the event does not appear in the relevant log, the event did not occur, there is no notification to troubleshoot.

Step 2: Check the delivery history

  1. Go to Settings → Notification Channels → Delivery History.
  2. Find the event in the log (filter by date and event type).
  3. Check the delivery status:
  • Delivered: the notification was sent successfully. The issue is in your receiving end (spam filter, channel settings).
  • Failed: CloudAIPilot attempted delivery but it failed. Read the error message.
  • No entry: the notification was never attempted. Check channel status and preferences.

Step 3: Follow the diagnosis path

If status is "Delivered" but you did not receive it

Email channels:

  • Check your spam/junk folder.
  • Check if your email client has a filter that auto-archives or deletes messages from the sender domain.
  • Verify the email address in the channel config matches your inbox.

Slack channels:

  • Check that you are in the channel where the bot posts.
  • Slack may have channel mute or notification settings that suppressed the notification.

Telegram channels:

  • Check that you have not muted the bot in Telegram settings.

If status is "Failed"

Read the error message in the delivery log. Common fixes:

Slack/Teams/Discord "webhook URL invalid or expired" Fix: Re-create the webhook in your messaging platform and update the URL in CloudAIPilot.

Email "rejected by server" Fix: The recipient email server rejected the message. Try a different email address or contact your email admin to allowlist the sender domain.

Telegram "bot blocked" Fix: Open Telegram, find your bot, and click Unblock or Start.

Webhook "connection timed out" Fix: Your webhook endpoint is not responding. Verify the destination URL is online and accepting POST requests.

If there is no delivery log entry for the event

Cause A: No active channels Fix: Go to Settings → Notification Channels and verify at least one channel is Active (green power icon). If all channels are Paused, no notifications are sent.

Cause B: Event type is disabled in your preferences Fix: Go to Settings → Notification Channels → My Alert Preferences and verify the event type is checked.

Cause C: Alert was in Snoozed state When an alert is snoozed, repeat notifications for that alert are suppressed during the snooze window. Fix: Check the alert status in Alerts → Events.

Cause D: Digest mode delayed the notification Fix: If the channel uses a digest mode (15-min, 1-hour, daily), notifications are batched. Wait for the next digest window to confirm the notification is included.

What success looks like

  • After fixing the underlying cause, test the channel (Test button) to confirm delivery works.
  • The next real event produces a successful delivery log entry.

Related articles