Fajita separates two questions so alerts stay trustworthy.
| Step | Answers |
|---|---|
| Check retry | Was this one failed request temporary? |
| Incident verification | Is the service meaningfully unhealthy? |
The sequence
A scheduled check fails. Fajita retries the request. If the retry also fails, the failing result becomes eligible for verification. Verification counts consecutive eligible failures against the monitor's failure confirmation threshold. When the threshold is met, an incident opens. If a check passes before the threshold, the monitor returns to operational.
Verification threshold
Each monitor has a failure confirmation threshold, defaulting to two consecutive eligible failures. Critical monitors can open faster. A single failing check never opens an incident on a normal monitor.
Why this matters
- A retry result stays in history so you can see what happened.
- Manual tests do not open incidents.
- Platform uncertainty (a problem on Fajita's side) does not automatically blame your service.