Troubleshoot alert delivery

Confirm the alert and scope

1. Verify the alert is active, not expired or cancelled.
2. Confirm the device and selected location belong to the same tenant.
3. Check that the alert targets that location and the device has not been revoked.

Check client health

1. Review the latest heartbeat and installed version.
2. Confirm outbound HTTPS and secure WebSocket access to the documented API hostname.
3. Restart the client and confirm polling fallback retrieves the active alert.
4. Capture timestamps and request identifiers before contacting support.

Check source health

For NWS alerts, confirm the source is enabled, its geography matches the authoritative alert, and its severity/event filters permit delivery. Provider failures and no-match results are different conditions.

Check an outbound destination

1. Confirm the destination is active and its action, origin, severity, and location filters match the alert.
2. Run the non-emergency destination test after verifying the endpoint and provider contract.
3. Review the dispatch state, safe error code, attempt history, and next retry time.
4. For a dead letter, correct and retest the destination before an authorized operator requests another bounded retry cycle.