My alert didn't fire

If a sync produced a change event that appears in the Incidents view but the corresponding alert did not arrive in your channel, the cause is almost always related to alert routing rather than alert delivery. Work through the checks below in order.

1. Confirm the change is recorded

Open the Incidents view from the left navigation. If the change appears there, the diff engine and the change-event pipeline are functioning correctly, and the issue is between the change event and the alert dispatch.

2. Review alert preferences for the dependency

Alert preferences are configured per dependency. Open Dependencies → [integration] → Edit and locate the Alert preferences panel. For each preference rule, verify:

• Minimum severity — a rule with min_severity: breaking will not dispatch on risky or safe changes.
• Channels — a rule with an empty channel list permits all configured channels; a non-empty list restricts to the listed channels only.

A common pattern is to restrict PagerDuty to Breaking and inadvertently apply the same restriction to Slack, leaving Risky changes without a destination.

3. Confirm the channel is reachable

For Slack, confirm that the integration is still connected at Settings → Integrations. If the workspace administrator revoked the application, reconnect to restore alert delivery.

For PagerDuty, verify that the routing key on file is still valid and the corresponding service is active.

For email, confirm that the recipient address is correct in Settings → Notifications and check the spam folder.

4. Account for cause-grouping

When a single underlying schema change affects many endpoints, Intello consolidates the resulting events under a shared cause and dispatches one alert per cause rather than one per endpoint. The other affected events are present in the Incidents view but do not produce additional alerts. The change card surfaces related events under the same cause so you can see the full impact.

This is the intended behaviour for high-fan-out changes; if a separate per-endpoint alert is what you expected, the absence is correct.

5. Account for plan-driven alert delay

Alerts on the Starter plan are delayed by six hours after the change event is generated. If the alert has not arrived but the change appeared recently, the alert may still be queued. On Pro and above, alerts are dispatched as soon as the sync produces a change event; if you are on a higher tier and the alert has not arrived after several minutes, the cause is more likely to be in routing or channel reachability.