Monitoring
Solutions
Resources
Free Tools
Pricing
Products / Server monitoring / Cron Jobs Monitoring
Heartbeat monitoring for scheduled tasks

Cron Jobs Monitoring

Cron fails silently: no error, no email, just work that quietly stops happening. Add one line to your job and Upzilla tells you when a scheduled task did not run.

9 check locations1–120 min check interval8 alert channels10 monitors free
nightly-backup.sh
Last check-in2 h ago
Expected every24 h
Statuson schedule
Missed runs (30 d)0
Illustrative example of a check result.

The job that never ran

Backups, reports, invoices, cleanups: many critical tasks depend on cron. When one stops (a server rebooted, a path changed, a disk filled) nothing complains. You find out when you need the backup.

Cron monitoring flips the problem around. Instead of watching the server, Upzilla expects your job to check in. If the check-in does not arrive on time, you are alerted.

What Upzilla checks

Every check is stored in a full log, so you can see exactly when and how something changed.

One-line setup

Generate a key with a direct link and call it from your cron entry when the job completes.

Missed-run alerts

Get notified as soon as an expected check-in does not arrive.

Full check log

See every run with its time, so patterns are obvious.

Status page

Show your team or clients the health of scheduled tasks.

How it works

From sign-up to your first alert in a few minutes.

Create the monitor

Upzilla generates a key and a link for it.

Add the call to your job

For example, append a curl request to the end of the cron line.

Get alerted

If the call does not arrive on time, your channels are notified.

Settings you can control

Sensible defaults get you started; every option below can be tuned per monitor.

SettingWhat it does
Input webhookThe link your job calls when it finishes. Webhooks are configured under Integrations / Webhooks in your account.
FrequencyHow often the check runs: 1 to 120 minutes. The Free plan checks from every 15 minutes; Premium from every minute.
LocationsRun the check from one or several of 9 locations: Spain, France, United Kingdom, USA (New York, Los Angeles), Australia, Singapore, Japan and Germany.
NotificationsPick any of your pre-configured alert channels: e-mail, SMS, Telegram, Slack, Messenger, voice call, webhooks and more.
Status pageMake the statistics of this monitor public or private.
TagsGroup monitors with tags to keep large accounts tidy.
IP versionForce IPv4, IPv6, or let Upzilla use whichever is available.
Full setup guide in the documentation →

Common use cases

Backups

Know immediately when a nightly backup did not finish.

Data imports and exports

Watch ETL and report jobs.

Billing runs

Protect invoicing and renewal jobs.

Cleanup and maintenance

Catch silent failures of housekeeping scripts.

Alerts where your team already is

Create as many notification methods as you like, even on the free plan.

Slack
Telegram
Telegram group
Facebook Messenger
Email
SMS
Voice call
Webhooks

Related monitors and tools

Uptime MonitoringHTTP(S) MonitoringSSH MonitoringWeb Server MonitoringCron Expression Parser (free tool) →

Questions about cron jobs monitoring

How does it know a job ran?

Your job calls a unique link when it completes. Upzilla expects that call within the interval you set.

Will it tell me why a job failed?

It tells you that the job did not check in. Use your job’s own logs to find the cause.

Do I install anything on the server?

No agent is needed. A single HTTP request from the job is enough.

Is there a helper for cron syntax?

Yes, our Cron Expression Parser explains any schedule and shows the next runs.

Stop finding out about failed cron jobs the hard way

No card required. 10 monitors of any type, free.

Create free account →