Understand the direction of the check
UptimeRobot’s cron-monitoring documentation describes a job sending a request to a unique monitoring URL, with an alert when the expected signal does not arrive in time. This differs from an external observer repeatedly requesting a public web page. The distinction matters because the meaning of the heartbeat depends on where and how the operator places the signal in the job. A received request is not automatically proof of every downstream result.
Write the completion condition
Ask the responsible maintainer what must be true before the job should signal success. Starting, finishing and producing a usable output can be different milestones. Do not add a heartbeat to a business process without understanding those distinctions. Keep the monitoring URL protected according to the operator’s practices, and do not place it in public documentation or examples where other people could trigger misleading observations.
Use a fictional report job
Suppose a scheduled process creates a daily internal report. A signal at startup says the process began; it does not prove the report was produced or delivered. A signal tied to a verified completion condition answers a stronger question, though the report may still need separate content validation. This example explains the evidence boundary without providing an unreviewed script or changing any real scheduled job.
Maintain the schedule assumption
Record the expected timing, allowed delay and owner of schedule changes. If a business intentionally changes the job’s schedule, its monitoring expectations need review too. Do not repeatedly widen a grace period to hide unexplained failures. Preserve the missed-signal evidence and investigate through the normal operator. Heartbeats complement other observations; they are not a substitute for backups, recovery tests or confirming that a business process remains useful.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- UptimeRobot: cron-job monitoring — Merchant documentation · uptimerobot.com · Merchant-controlled · checked 2026-09-26