Skip to content
English
  • There are no suggestions because the search field is empty.

An expected notification didnt arrive

Summary

Something happened in the platform and the alert never reached your channel, inbox, or ticket queue. There is one place that tells you which of those three it was, whether the platform tried to send it, suppressed it as a repeat, or failed, so start there rather than guessing.

Steps / Answer

Before you start

Notification configuration lives at Integrations → Notifications and requires the Manage Communications permission, plus Manage Users or Manage Tenant to open Configure. Which integrations you can use there depends on your plan, and whether Slack and Microsoft Teams can be connected at all depends on how CyberHQ.ai is set up for your organization.

1. Check the Delivery log

At the bottom of the notifications page, View delivery log opens a shared Delivery log covering recent send attempts across every integration. For each attempt it shows when, through which channel, at what severity, and the outcome: with the specific error if there was one. Three outcomes, three different meanings:

  • Sent: the platform delivered it. The problem is on the receiving side: the channel, the mailbox, or a filter there.
  • Deduplicated: intentionally suppressed as a repeat of something already sent. This is by design, so nothing needs fixing here.
  • Failed: read the error shown; it usually names the cause directly.

If there is no entry at all, or the log reads "No notifications sent yet.": nothing was attempted. Go to step 2.

The daily briefing email is recorded separately: select View briefing history in the Daily CISO briefing section to see each briefing that went out and any recipients it failed to reach.

2. Check the destination is enabled and not filtered out

Each destination can be switched off independently, and each can be filtered to specific event types, severities, or signal types. A filter narrower than the event you expected will silently exclude it.

Empty filters mean "everything": so an over-specified filter is far more often the cause than a missing one.

3. Check the underlying integration is still connected

Slack and Teams destinations depend on that integration being connected. If it has been disconnected, any destination pointing at one of its channels stops delivering until it is reconnected. In the Slack integration you can also confirm whether interactive buttons (acknowledge/resolve directly from a message) are active, and whether an authorized-responder list is limiting who can use them.

4. If you rotated a signing secret

Rotating a secret takes effect instantly and the previous one stops working immediately. Anything receiving your notifications needs the new value. Note that secrets are shown exactly once, at creation or rotation: if it wasn't copied then, generate a new one and update the receiving system.

5. Test the path directly

Rather than waiting for the next real event, trigger one:

  • Notification destinations each have a Test button on their row (Test to me for a destination that messages each person privately). It sends a test message through that destination, and the result shows under the row.
  • Ticketing connectors have a test that performs a live connection check and reports either the connected account's name or a specific error.
  • The daily briefing has "Send test briefing now", which delivers exactly what recipients would receive. Briefing history shows every past briefing and its actual content.
  • Webhook subscriptions can be tested individually, one per event type.

If every channel is affected, check your email provider

An organization-wide failure of anything email-delivered, including the daily briefing, is often the email provider rather than any individual destination. Go to Integrations → Email provider and read the state it reports:

State

Sending?

Using the global email provider

Yes, via the platform's provider

Email delivery is off (global email provider)

No: nothing is being sent.

No per-tenant override is set…

Yes, via the platform's provider

Per-tenant provider active

Yes, via your provider

Per-tenant provider configured (email delivery is off)

No: nothing is being sent.

The two "off" states are the ones to look for. A provider that has been configured but has email switched off looks set up and delivers nothing.

If the notifications page says your settings are in an unrecognized format

If you see "Your stored notification settings are in an unrecognized format. Saving is turned off so they aren't overwritten.", your settings still exist and are still in force: the page has disabled saving to protect them. Don't try to clear and re-enter them; raise it with support.

One thing that catches people out

Each section of this page saves on its own. Destinations (Slack, Teams, ticketing, webhooks) save when you add, edit, or delete them, while the daily briefing card has its own Save briefing settings button. If you changed a briefing setting and navigated away without pressing it, that change was not applied, even though destination changes around it were.

Confirm it's resolved

Send a test through the affected path and confirm a matching Sent entry appears in the Delivery log. If the log says Sent and the message still hasn't arrived, the remaining investigation belongs on the receiving system.

Related