The silent failure

A job that never runs sends no error.

Cron does not tell you when something goes wrong. A server reboots at the wrong moment, a disk fills up, someone edits the crontab. Then the job simply does not happen, and nothing lands in your inbox. You find out weeks later, usually when you need the backup.

So turn it around. Instead of waiting for an error, expect a check-in. Every successful run pings UptimeClaw, and silence is the alarm.

Setup

How cron job monitoring works.

Each job gets its own push URL. You set when the job should run and how late it may be. Then you add one line to the job.

  • Create a push monitor. Pick the push type in the dashboard and copy its URL.
  • Set the schedule. A fixed interval, or a cron expression with your server's timezone.
  • Set the grace period. The longest normal run time, so a slow night is not an outage.
  • Add the ping. Append the curl line after the job, joined with &&.

Want failures reported straight away? Send /fail or the exit code. See the API docs for the full push reference.

Cron job monitoring timeline: a nightly job pings after each run, and a missed run raises an alert after the grace period

What you get

Everything a scheduled job needs to be watched.

Schedule-aware

Cron expressions and timezones

UptimeClaw knows when the next run is due, including jobs that only run on weekdays or once a month.

Grace period

No alarms for slow runs

A job that takes longer than usual still counts, until it passes the grace period you set.

Explicit failure

Fail fast when it breaks

Ping /fail or the exit code and the monitor goes down at once, without waiting for the schedule.

Context

A message with each ping

Send a short message in the request body, such as rows synced or a backup size, and see it in the check history.

Alerts

On the channel you watch

Missed runs alert by email, WhatsApp, Telegram, Slack, Discord, Microsoft Teams, PagerDuty or a webhook.

Recovery

Know when it is fixed

The next successful ping closes the incident and sends a recovery message.

Ways to watch scheduled jobs

Three common approaches, and what each one catches.

ApproachJob failed with an errorJob never ranWorks when the server is down
Cron's own email (MAILTO)Only if the job printed output and mail delivery worksNoNo
Log checks on the same serverYes, if someone reads themNot reliablyNo
Push URL (heartbeat check)Yes, with /fail or the exit codeYes, the ping is missingYes, the alert comes from outside

Cron mails a job's output to MAILTO only when there is output. See the crontab manual.

Troubleshooting

The usual reasons a check-in goes wrong.

SymptomLikely causeFix
Alert says late, but the job ranGrace period shorter than the run, or a timezone mismatchRaise the grace period, and set the timezone the server uses
No alert when the job failedThe ping runs even when the job failsJoin with &&, or send the exit code
The job hangs on the pingNo timeout on the requestAdd -m 10 to curl so the ping never blocks the job
No curl in the containerMinimal imageUse wget -q -O- URL, or any HTTP client

FAQ

Is cron job monitoring included on the free plan?

Yes. Push monitors are part of every plan, including the free one. Each scheduled job counts as one of your monitors.

Which schedules can I use?

Either a fixed interval, such as every 15 minutes, or a cron expression such as 0 3 * * *. Set the timezone your server uses.

What if a job sometimes runs long?

Set the grace period to the longest normal run time. UptimeClaw only raises an alert once the ping is later than the schedule plus the grace period.

Can a job report that it failed?

Yes. Call the push URL with /fail at the end, or with the exit code, such as /1. Anything other than 0 marks the monitor down straight away.

Does it only work with cron?

No. Anything that can make an HTTP request can ping it. That includes systemd timers, Kubernetes CronJobs, GitHub Actions and Windows Task Scheduler.

Where do the alerts go?

They go to the channels you choose, such as email, WhatsApp, Telegram, Slack, Discord, Microsoft Teams, PagerDuty or a webhook. A recovery message follows when the next successful ping arrives.

Silence is the alarm.

Cron job monitoring on the free plan. One line per job.

Related

API monitoring · All features · WhatsApp alerts · Alert integrations · API docs