When Will My Cron Job Run Next? Check Instantly
Table of Contents
Paste any cron expression into our free crontab visualizer and see the next 20 run times instantly — displayed in your local timezone on a calendar. No signup, no install.
Knowing exact future run times is essential before deploying: it catches timezone mistakes, off-by-one errors, and unexpected OR-logic behavior that you wouldn't notice just by reading the expression.
How to Check Your Cron Job's Next Execution Times
The fastest way: open the crontab visualizer, paste your expression, and the next 20 run times appear immediately. The calendar view shows them plotted by date so you can verify the pattern visually.
On Linux/Mac using the command line: There's no built-in cron --next command, but you can calculate next runs with the croniter Python library or by installing cronutils. The browser visualizer is faster for spot-checks.
Checking cron history (past runs): Check the syslog:
grep CRON /var/log/syslog | tail -20
# or on systems using journald:
journalctl -u cron --since "1 hour ago"This shows when cron jobs actually executed — useful for confirming a job ran (or diagnosing why it didn't).
Check Next Run Time by Platform
| Platform | How to check next run time |
|---|---|
| Linux crontab | No built-in command. Use the browser visualizer or python3 -c "from croniter import croniter; ..." |
| systemd timers | systemctl list-timers --all — shows next trigger time for every timer |
| Kubernetes CronJob | kubectl get cronjob <name> -o wide — shows SCHEDULE and LAST SCHEDULE |
| GitHub Actions | View the workflow's scheduled runs in the Actions tab. The schedule trigger shows last run; calculate next manually with the visualizer. |
| AWS EventBridge | Visible in the EventBridge console under the rule — shows next invocation time |
| Node.js node-cron | Use cronParser.parseExpression(expr).next().toISOString() from the cron-parser npm package |
For any platform, the browser visualizer gives you a quick pre-deployment sanity check without needing access to the server.
Sell Custom Apparel — We Handle Printing & Free ShippingWhy Your Cron Job Runs at Unexpected Times
Three common reasons the next run time doesn't match your expectation:
1. Timezone mismatch. Cron runs in the system's timezone, not yours. If your server is UTC and you're Eastern time, a job set to run at 9:00 runs at 4 AM your time (UTC-5 in winter). Always verify the server timezone with date before writing a cron expression with specific hours.
2. OR logic for day-of-month + day-of-week. 0 9 1 * 1 runs at 9 AM on both "the 1st of every month" AND "every Monday" — not just on Mondays that are the 1st. If you only set one of these fields, use * for the other to get purely date-based or purely weekday-based logic.
3. February/short-month edge cases. 0 0 31 * * won't run in February, April, June, September, or November — those months have fewer than 31 days. The crontab visualizer's calendar view makes this visible immediately.
Calculating Next Run Times for Special Cron Expressions
Certain expressions have non-obvious next run time behavior:
Expressions with large step values: 0 */12 * * * runs at midnight and noon — the next run after 1 PM is midnight (11 hours away), not in 12 hours from 1 PM.
Multi-value hour expressions: 0 6,18 * * * — if it's currently 7 AM, the next run is 6 PM (11 hours), not in 6 hours. The visualizer plots all 20 future runs so you can see the actual gap between executions.
Near-midnight boundary jobs: 55 23 * * * runs at 11:55 PM. If you set this job at 11:56 PM, the first execution is tomorrow at 11:55 PM — nearly 24 hours away. This surprises teams who expect the job to run "soon."
Paste any of these into the crontab visualizer and the calendar view makes the actual run pattern obvious before you deploy.
Try It Free — No Signup Required
Runs 100% in your browser. No account, no install, no limits.
Open Free Crontab VisualizerFrequently Asked Questions
How do I find out when a cron job last ran on Linux?
Check the system log: run "grep CRON /var/log/syslog | grep -i ran" or "journalctl -u cron --since yesterday" on systems using journald. Many cron jobs also write to their own log files if you redirect output in the crontab entry with >> /var/log/myjob.log 2>&1.
Why is my cron job not running at the time I set?
The most common cause is a timezone mismatch — your server clock is UTC and you wrote the expression in your local timezone. Check with "date" on the server to confirm the system timezone. Other causes: the cron daemon isn't running ("service cron status"), the script has a PATH problem (use absolute paths in cron), or the job ran but failed silently (redirect stderr to a log file to see errors).
Can I test a cron expression without running it on a server?
Yes. Use our browser-based crontab visualizer — paste the expression and see the next 20 run times immediately, no server required. This is the fastest way to verify an expression before deploying it.