Notification History
The notification history provides a log of every notification Odin Scan has dispatched. Use it to verify that alerts are reaching their destinations, identify failed deliveries, and track retry attempts.
Accessing Notification History
Navigate to Alerts > History in the Odin Scan dashboard.
History Table
Each entry in the notification history table displays the following information:
| Column | Description |
|---|---|
| Timestamp | When the notification was created |
| Channel | The channel name and type (Slack or email) that the notification was sent to |
| Status | Current delivery status (see below) |
| Attempts | Number of delivery attempts made so far |
| Message | A brief summary of the notification content, including the repository name and finding counts |
Delivery Statuses
| Status | Meaning |
|---|---|
| Delivered | The notification was successfully sent to the destination |
| Pending | The notification is queued and will be attempted shortly |
| Failed | Delivery failed on the most recent attempt but will be retried automatically |
| Dead Letter | All retry attempts have been exhausted and the notification was permanently marked as failed |
Retry Behavior
When a notification delivery fails (e.g., a Slack webhook returns an error or an email bounces), Odin Scan automatically retries:
- Up to 3 delivery attempts are made for each notification.
- Retries use exponential backoff – each subsequent attempt waits longer before trying again.
- If all 3 attempts fail, the notification is moved to Dead Letter status.
Dead letter notifications are not retried automatically. If you resolve the underlying issue (e.g., fix a revoked webhook URL), you can create a new channel and policy to resume notifications going forward.
Unread Notifications
The bell icon in the dashboard header displays a badge with the count of unread notifications. Clicking the bell opens a dropdown with recent notifications.
From the notification history view, you can:
- Mark as read – click on an individual notification to mark it as read.
- Mark all as read – use the bulk action to clear all unread notifications at once.
Marking a notification as read only affects the unread badge count. It does not change the delivery status or remove the entry from the history.
Troubleshooting Failed Deliveries
If you see Failed or Dead Letter notifications, check the following:
- Slack – verify that the webhook URL is still valid. Slack webhooks can be revoked if the associated app is uninstalled or the channel is deleted.
- Email – verify that recipient addresses are correct and that Odin Scan emails are not being blocked by spam filters.
- Channel status – confirm the channel is still enabled in Alerts > Channels.
Next Steps
- Channels – manage or update channel configurations
- Alert Policies – adjust which findings trigger notifications
- Overview – return to the notifications overview