Why it matters
Manual check matters because teams need a shared, precise meaning for an on-demand test run outside the normal schedule. 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, an on-demand test run outside the normal schedule 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 manual 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 manual check, the team treats that change as a reliability event with a clear owner and next step.
Common misconception
Manual checks replace scheduled monitoring
That reading usually collapses distinct ideas into one slogan. Keep manual check tied to observable behavior so the definition stays useful under pressure.
How Fajita handles this
Fajita lets you test a monitor before save and run manual checks later for diagnosis.