Cron expression tester › 0 */2 * * *
What does 0 */2 * * * mean?
Every 2 hours. Runs at 00:00, 02:00, 04:00 … 22:00 — twelve times a day.
Handy for moderately heavy jobs — batch imports, reindexing, or reports that don't need to be hourly.
Next scheduled runs
Calculating…
Field-by-field breakdown
| Value | Field | Meaning |
|---|---|---|
0 | Minute (0–59) | exactly 0 |
*/2 | Hour (0–23) | every 2 step |
* | Day of month (1–31) | every value |
* | Month (1–12) | every value |
* | Day of week (0–6, Sun=0) | every value |
Standard 5-field Vixie/POSIX cron: minute hour day-of-month month day-of-week. Cron uses the server's local timezone unless configured otherwise. Non-standard extensions (@daily, L, W, #, seconds) aren't evaluated here.
Open this schedule in the interactive tester →
Will you know if a every 2 hours run is skipped?
Knowing when 0 */2 * * * should fire is only half of it. The failure that hurts is the silent one — the box was asleep, the trigger broke, the token expired, and nobody noticed. Cronpulse is a free dead-man's-switch: your job pings a URL each time it runs on this schedule, and if a ping goes missing, we alert you by email, Discord, Slack, or webhook.
Monitor a every 2 hours job — free → No signup needed to start.
Related cron schedules
| Schedule | Meaning |
|---|---|
0 */3 * * * | Every 3 hours |
0 */4 * * * | Every 4 hours |
0 */6 * * * | Every 6 hours |
0 */12 * * * | Every 12 hours |
0 0 * * * | Every day at midnight |
All common cron expressions → · Monitor scheduled jobs → · Monitor an AI agent →