Why it matters
Scheduled check matters because teams need a shared, precise meaning for a single execution of a monitor on its interval. Vague language turns incidents into arguments about words instead of fixes.
When everyone uses the same definition, alerts, status updates, and post-incident reviews stay aligned.
How it works
In practice, a single execution of a monitor on its interval shows up as a concrete signal you can measure or communicate. Operators define what good looks like, watch for deviations, and record what happened when expectations break.
The useful version of scheduled check is operational: it changes who gets notified, what customers see, or which metric a team reviews after an incident.
Practical example
Imagine a team running checks against https://api.example.com/health. When the observed behavior stops matching the definition of scheduled check, the team treats that change as a reliability event with a clear owner and next step.
Common misconception
A scheduled check is a manual test you click
That reading usually collapses distinct ideas into one slogan. Keep scheduled check tied to observable behavior so the definition stays useful under pressure.
How Fajita handles this
Fajita records each scheduled check in monitor history. See check intervals.