Standard 5-field cron syntax and Vixie macros
Every standard crontab line uses five space-separated fields in strict order: minute, hour, day of the month, month, and day of the week. Typing */15 9-17 * * 1-5 into Cron expression displays each token directly above its field name and translates the schedule into plain English immediately.
Field order, allowed ranges, and named months or weekdays
Minute values span 0 through 59 and hour values span 0 through 23 on a 24-hour clock. Day of the month accepts 1 through 31, month accepts 1 through 12 or three-letter names JAN through DEC, and day of the week accepts 0 through 7 or SUN through SAT where both 0 and 7 represent Sunday.
| Field | Allowed values | Wildcards & operators | Example |
|---|---|---|---|
| Minute | 0–59 |
*, ,, -, / |
*/15 (every 15 min) |
| Hour | 0–23 |
*, ,, -, / |
9-17 (9 AM to 5 PM) |
| Day (month) | 1–31 |
*, ?, ,, -, / |
1,15 (1st and 15th) |
| Month | 1–12 or JAN–DEC |
*, ,, -, / |
JAN-MAR (Q1) |
| Day (week) | 0–7 or SUN–SAT |
*, ?, ,, -, / |
1-5 (Mon through Fri) |
If you are building log parsers or validation rules alongside your scheduled jobs, test matching strings with the JavaScript regex pattern tester in another tab.
Vixie cron macros and the POSIX crontab standard
The parser follows the POSIX.1-2017 crontab Utility Specification for numeric fields and also expands seven Vixie cron shorthand macros: @yearly, @annually, @monthly, @weekly, @daily, @midnight, and @hourly. Entering @daily expands internally to 0 0 * * *, while @reboot displays a clear notice explaining that startup triggers have no recurring calendar schedule.
Cron schedule next run times and UTC time zones
Reading a schedule in plain English catches syntax mistakes, yet seeing concrete calendar dates prevents off-by-one-hour bugs across time zones and daylight saving transitions. The Next runs card calculates the next 8 execution timestamps and refreshes every 30 seconds as the clock advances.
Previewing eight upcoming runs in your local time zone
Each entry in Next runs formats the weekday, date, hour, and minute in your browser’s active IANA time zone alongside a relative countdown such as in 12 minutes. When an expression targets an impossible calendar date such as 0 0 30 2 * for February 30, the panel reports that the job never runs instead of hanging.
To align server logs or Unix epoch fields with those scheduled timestamps, convert UTC epoch timestamps to local time directly in your browser.
GitHub Actions and Kubernetes CronJob UTC offsets
GitHub Actions workflow schedule triggers and default Kubernetes CronJob Schedule Documentation controllers evaluate expressions in UTC unless a cluster timeZone field is explicitly configured. Because Next runs renders in your local device time zone, subtract or add your UTC offset before deploying 0 9 * * 1-5 to a cloud pipeline.
Six-field Quartz expressions that prepend seconds or append a year fail validation intentionally with an explicit field-count error so you never deploy an incompatible string to a 5-field runner.
How does cron day-of-month and day-of-week OR logic work?
When both the third field (day of the month) and fifth field (day of the week) are restricted rather than left as *, standard cron combines them with OR logic rather than AND logic. A schedule such as 0 0 15 * 5 runs on the 15th of every month and also on every Friday, not solely on Fridays that land on the 15th.
Why restricting both day fields runs more often than expected
As documented in the Linux crontab(5) Manual Page, day-of-month and day-of-week are unioned whenever neither field is a wildcard. Leaving one of the two day fields as * avoids accidental extra runs, and any combined condition such as “first Monday of the month” should be checked inside the executed script.
Tip: Never write
*/0or backwards numeric ranges like17-9; the parser catches zero steps and inverted ranges immediately before they fail silently in production crontabs.
Step values in the cron minute field and boundary resets
Step expressions such as */15 in the minute field reset at the top of every hour, firing at minutes 0, 15, 30, and 45 rather than counting 15 min from when the daemon started. Similarly, */7 in the minute field fires at 0, 7, 14, 21, 28, 35, 42, 49, and 56, followed by a shorter 4 min gap to 00 of the next hour.
When documenting a deployment runbook or team wiki, you can export crontab and workflow snippets as PNG cards for clear visual reference.
Verifying schedules with presets before production deploy
Eight clickable preset pills sit directly under the plain-English readout: Every minute, Every 5 minutes, Hourly, Daily at midnight, Weekdays 09:30, Weekly (Sunday), Monthly, and Yearly. Clicking any pill populates Cron expression with a known-good baseline that you can adjust one field at a time.
Expanding Cheat sheet reveals a compact reference for *, ,, -, /, JAN-DEC, SUN-SAT, and @daily macros without leaving the workspace. Testing edge cases such as 30 9 * * 1-5 or 0 0 29 2 * before committing helps confirm whether a schedule runs every weekday or only once every four leap years.
Before editing a live production crontab file or CI YAML trigger, compare your old and updated configuration lines side by side with Text diff so accidental field shifts stand out immediately. Every expression is parsed locally in JavaScript with zero server requests, keeping internal deployment schedules private.