Cron job monitoring with heartbeat deadlines you can reason about
Heartbeat monitors work in the opposite direction from active network checks: your cron job or scheduled task sends an authenticated POST to the monitor heartbeat endpoint. When the grace deadline passes without a valid push, that check fails; DOWN and incident state still follow the configured consecutive-failure threshold.
Each heartbeat monitor gets a dedicated secret token. POST /api/v1/heartbeat/:publicId records an UP heartbeat only when the token is supplied as Authorization: Bearer <token>. The token is distinct from the public monitor ID and never belongs in the URL or query string.
At the configured grace deadline, a missing heartbeat causes a failed check. The monitor becomes DOWN and opens an incident only after the configured confirmation threshold is reached; with the default threshold of 2, a later scheduled evaluation provides the second consecutive failure.
A received heartbeat immediately records UP, clears stale scheduler ownership and resolves an open incident. Missed deadlines follow the normal incident pipeline.
What UptimeSure checks
- Last heartbeat time
- Configured grace period
- Missed-heartbeat deadline
- Push/recovery state
Common use cases
- Cron jobs
- Scheduled backups
- ETL/import tasks
- Periodic workers or integration jobs
Configuration
- Heartbeat grace period
- Check interval policy
- Confirmation threshold
- Alert associations
Alerts and recovery
Link standard alert channels for missed-job DOWN and recovery notifications.
Example
Example: a nightly backup POSTs to /api/v1/heartbeat/:publicId with its secret in the Authorization: Bearer header. If the grace deadline passes without a push, the missed-heartbeat check fails; DOWN and an incident follow only after the configured consecutive-failure threshold.
Frequently asked questions
Should I put the heartbeat token in public code?
No. Treat the token as a secret credential, keep it in the scheduled job configuration, and send it only in the Authorization header.
Can a late heartbeat recover the monitor?
Yes. A valid push records UP and resolves the open missed-heartbeat incident.
Does V1 run my cron job?
No. UptimeSure watches for the heartbeat; your scheduler still runs the job.
Explore UptimeSure
Start monitoring
Sign in to configure this monitor type and connect the alerts your account uses.