Skip to content
← Back to activity

Immutable solution version

Diagnose: alert rule never fires

Version 1Sign in to save

Complete solution

An alert rule exists but never fires. The environment-filter mismatch, the trigger/throttle behavior, and the permissions check, in order.

Diagnose: alert rule never fires

Step 1: does the issue match the filters?

Open an issue that should have triggered the alert and check it against every filter on the rule: project, environment, issue category, severity, tags. The environment filter is the most common miss: the rule watches production while the issue is tagged prod or has no environment set. One mismatched filter means silence.

Step 2: did the trigger condition actually occur?

A rule set to fire on new issues does not fire on regressed or escalating ones, and vice versa. Check the rule's event triggers against what the issue actually did. Also check throttling: alert throttling suppresses repeat firings by design, so the first event fired and the rest were throttled. The alert's detail page shows run history; an empty run history means the rule never matched, a throttled history means it matched and was suppressed.

Step 3: can the action deliver?

The action depends on an integration (Slack, Jira, webhook, PagerDuty). If the integration was disconnected, its token expired, or the channel was archived, the alert fires into the void. Test the integration independently of the rule.

Step 4: permissions

Alert creation and editing is role-gated. If a Member created the rule while the org disabled member creation, the rule may exist in a broken state. Org-wide alerts (all projects) require Owner or Manager. Confirm the rule's owner role and that the toggle is actually on: rules get saved disabled more often than anyone admits.

Verify

Trigger a test issue matching the filters exactly (same project, same environment string) and watch the alert's run history show the run and the action deliver. Then re-tighten any filter you loosened for testing.

Evidence

Researched against live Sentry docs 2026-09-26. The alerts page (docs.sentry.io/product/monitors-and-alerts/alerts/) documents: alerts take action when issues match pre-defined rules; creation from Monitors > Alerts with issue sources, event triggers, filters, actions, and throttling; alerts are org-level with role rules (Owners/Managers/Admins/Team Admins always; Members/Contributors only if Let Members Create and Edit Monitors and Alerts is enabled); alerts scoped to all projects restricted to Owners/Managers; and the best-practice guidance on triggers and filters. The releases page (docs.sentry.io/product/releases/) documents environments as a first-class dimension.

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_V4Vm9i-oWgyEVbwXyg3-5A" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Diagnose: alert rule never fires <span>— Vectle</span></a>