Free tools · no login

◷ Cron expression explainer

The cron expression 0 10 * * 6,0 means: at 10:00, on Saturday and Sunday. In UTC its next runs are Sat 2026-10-17 10:00 and Sun 2026-10-18 10:00. A heartbeat monitor with a 60-minute grace period, pinged at the end of each run, alerts you when the job stops running or fails silently.

Paste a 5-field cron expression. Get what it means in plain English, when it runs next, and what could go wrong. Nothing is sent anywhere; it runs on our server in a few milliseconds.

Try: */5 * * * * (every 5 minutes) · 0 9 * * 1-5 (weekdays 09:00) · 0 0 1 * * (monthly) · 30 2 * * 0 (Sundays 02:30) · 0 9 1-7 * 1 (the OR trap) · @daily (macro)
0 10 * * 6,0
At 10:00, on Saturday and Sunday.
minutehourday of monthmonthday of week
010**6,0
01031 values1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 120, 6

Next 10 runs · UTC

  1. Sat 2026-10-17 10:00 UTC (+00:00) · in 4d 13h
  2. Sun 2026-10-18 10:00 UTC (+00:00) · in 5d 13h
  3. Sat 2026-10-24 10:00 UTC (+00:00) · in 11d 13h
  4. Sun 2026-10-25 10:00 UTC (+00:00) · in 12d 13h
  5. Sat 2026-10-31 10:00 UTC (+00:00) · in 18d 13h
  6. Sun 2026-11-01 10:00 UTC (+00:00) · in 19d 13h
  7. Sat 2026-11-07 10:00 UTC (+00:00) · in 25d 13h
  8. Sun 2026-11-08 10:00 UTC (+00:00) · in 26d 13h
  9. Sat 2026-11-14 10:00 UTC (+00:00) · in 32d 13h
  10. Sun 2026-11-15 10:00 UTC (+00:00) · in 33d 13h

Times are UTC, which is what most cloud servers and GitHub Actions use. Set a timezone above to see local times.

Watch out

✓ No gotchas specific to this expression.

Always true for crontab: it runs in the server's timezone (check with date), with a minimal PATH, and % must be escaped as \%.
Full guide with systemd, Kubernetes and GitHub Actions examples: Every weekend (Saturday and Sunday)

Monitor this job

cron never tells you when a job stops running. Add a heartbeat ping after the command: Vigil expects it on this schedule and alerts you if it doesn't arrive within the grace period (we'd suggest 60 minutes here).

crontab -e
0 10 * * 6,0 /usr/local/bin/my-job.sh && curl -fsS -m 10 --retry 3 -o /dev/null https://puzaricloud.in/ping/<your-token>
Report start, finish and exit code (catches failures and hangs, not just silence)
0 10 * * 6,0 curl -fsS -m 10 -o /dev/null https://puzaricloud.in/ping/<your-token>/start; /usr/local/bin/my-job.sh; curl -fsS -m 10 --retry 3 -o /dev/null https://puzaricloud.in/ping/<your-token>/$?

Replace /usr/local/bin/my-job.sh with your command and <your-token> with the token Vigil gives you. && means the ping only goes out when the job succeeded.

Watch this schedule — get alerted if it doesn't run

Link to this result:
How Vigil can watch this for you

Know the moment a cron job doesn't run

Paste the same expression into a Vigil heartbeat. Vigil works out when each run is due in your timezone, waits the grace period, then alerts you if the ping never came, if the job reported a failure, or if it started and never finished.

Monitor a cron job free
Free plan, no card. Alerts on email, Telegram, Slack, Discord, Teams or any webhook.
More free tools:
◔ SLA & uptime calculator◇ DNS & email auth check⇄ HTTP request tester All tools →