The error log is empty.
Did the job ever start?
Enter a fixed UTC schedule and observed run timestamps. Find scheduled slots with no observation, late observations and repeated entries. Nothing is uploaded; no scheduler, monitoring account or third-party service is connected.
Check reported schedule coverage
Only paste fictional or authorized, non-sensitive timestamps. Use exact UTC YYYY-MM-DDTHH:mm:ssZ. This tool handles fixed-duration intervals, not cron syntax, daylight-saving schedules or business calendars.
Check whether the window has finished. Future or still-open time slots can show as “missing” in a timestamp-only report even though they are not yet overdue. The result now warns using your device clock, which is not independently verified. The fictional demo is deliberately independent of the current date.
Start with the fictional example. Missing observations require human investigation.
What this check can and cannot tell you
Missing exports, disconnected monitoring or a clock error can all leave the same gap. An observed timestamp does not show whether the work succeeded, delivered an outcome, or met customer acceptance.
The block produces a versioned, count-only review. It accepts up to 24 hours and at most 96 expected slots. Every observed timestamp is assigned to the preceding fixed UTC slot; an observation so delayed that it lands in a later slot cannot reliably be attributed to its original intended run.
Use your scheduler's own execution history and an independent observation of the final business result to confirm the cause. For simple schedules, a spreadsheet with generated timestamps is an excellent free alternative.
Why a monitor can disappear without raising an error → · Check supplied business outcome snapshots separately → · Privacy →