Symptom
A confirmed incident did not produce an alert in your channel.
Most likely causes
- No routing rule connects the monitor to the channel.
- The channel is paused or its credential is invalid.
- Quiet hours suppressed or delayed the alert.
- The destination rejected the delivery.
How to confirm
Open the channel's delivery history. Each attempt shows its status and any error category.
Resolution
- Add or fix a routing rule that references the channel.
- Re-test the channel and replace an invalid credential.
- Retry a dead-lettered delivery after fixing the destination.
What Fajita records
Every attempt is recorded with a status and an error category, and repeated failures move a delivery to a dead-letter state.
When to contact support
If deliveries show as sent but never arrive, contact support with the delivery reference.