Build and decode cron schedules in plain English, and see exactly when the job will next run.
In plain English
Next 5 runs (your local time)
Cron jobs fail quietly. The server reboots, a credential expires, the disk fills — and the job simply stops running with nobody the wiser until someone notices missing data days later.
Pingura heartbeats give each job a URL to ping when it completes. If the ping does not arrive on schedule, you get an alert. Five heartbeats are included free.
How heartbeats workIn order: minute (0–59), hour (0–23), day of month (1–31), month (1–12), and day of week (0–7, where both 0 and 7 mean Sunday). An asterisk means "every value" for that field.
The slash is a step value. */5 in the minute field means "every 5th minute" — so 0, 5, 10, and so on. You can combine it with a range too: 0-30/10 means minutes 0, 10, 20, and 30.
This is the most common cron surprise. When both fields are restricted, most cron implementations run the job when EITHER matches, not both. So "0 0 1 * FRI" runs on the 1st of the month AND on every Friday. This tool follows that behaviour.
You do not, unless something is watching. A cron job that silently stops firing is one of the most common causes of quiet data loss — no error, no alert, just nothing happening. Pingura heartbeats give your job a URL to ping when it finishes; if the ping does not arrive on schedule, you get alerted.
Free plan includes 5 heartbeat monitors. No credit card required.
Get Started Free