How the five fields work
A standard cron expression is five space-separated fields followed by the command to run. From left to right they are: minute (0–59), hour (0–23), day of the month (1–31), month (1–12), and day of the week (0–6, where both 0 and 7 mean Sunday). An asterisk means “every value” for that field, which is why * * * * * runs once a minute, every minute, forever.
Most real schedules are built from a handful of patterns: a fixed minute with a wildcard hour (5 * * * *), a fixed minute and hour with wildcards after it (30 2 * * *), or a step value that repeats inside a range (*/10 9-17 * * 1-5). The builder exposes each of those as a dropdown choice, and a custom option for anything the menu does not cover, such as lists (1,15) or ranges (1-5).
- Step values:
*/5in the minute field means every five minutes starting at minute 0;5/10means every ten minutes starting at minute 5. - Ranges:
1-5in the day-of-week field covers Monday through Friday. Ranges work in every field. - Lists:
1,15,30runs on the 1st, 15th and 30th of the month. Lists can mix with ranges and steps. - Names: many cron implementations accept
MON,JANand similar three-letter names, but numeric values are portable across cronie, Vixie cron, BusyBox and Quartz.
Presets that cover most jobs
The preset row exists because most schedules are boring: hourly, daily, weekly, or on weekdays. Starting from a preset and changing one field is faster and safer than typing an expression from memory.
- Every minute:
* * * * *— monitoring probes and queue drains, usually too frequent for a database backup. - Every 5 minutes:
*/5 * * * *— polling jobs and cache warmers. - Every hour on the hour:
0 * * * *— reports, rollups, health checks. - Daily at midnight:
0 0 * * *— cleanup and rotation jobs, but see the timezone note below. - Weekdays at 09:00:
0 9 * * 1-5— business-hour notifications and digest emails. - First of the month:
0 0 1 * *— invoicing and monthly accounting exports.
Timezones: the source of most “cron is broken” reports
Cron does not use your laptop's timezone. It uses the timezone of the machine or container where the daemon runs, which is often UTC on servers. A job you built as “9 AM” can therefore fire at 9 AM UTC — 5 PM in Shanghai, 1 AM in San Francisco — and look like it never ran at the right moment.
Use the timezone selector to preview the schedule against the timezone the job will actually execute in. If your server runs UTC and you want 9 AM local business time, convert first and encode the UTC hour in the expression, or set CRON_TZ=Asia/Shanghai at the top of the crontab (supported by cronie and Vixie cron, not by all minimal containers).
Daylight saving transitions are the second trap. When clocks jump forward, an expression fixed at 02:30 can be skipped; when clocks fall back, it can run twice. Jobs that must run exactly once should be idempotent, or should be moved to a scheduler that understands wall-clock time explicitly.
If the next-run preview and production disagree, compare date output on the server with the timezone you selected here. That mismatch explains most cases.
A copy-paste workflow that avoids silent failures
A crontab line has five schedule fields and then the command. Keep the command absolute-path based, redirect both stdout and stderr to a log file, and test the exact command once by hand before saving the line. Cron runs with a minimal environment, so python or node may not be on PATH even when they are in your shell.
# m h dom mon dow command
0 9 * * 1-5 /usr/bin/python3 /srv/app/report.py >> /var/log/report.log 2>&1
*/5 * * * * /usr/bin/curl -fsS http://127.0.0.1:8080/health >/dev/null 2>&1
When cron is the wrong tool
Cron has no retries, no dependency graph, no distributed locking, and no concept of “run once across three servers”. If a job must survive a failed host, run exactly once per cluster, or depend on another job finishing, use a workflow scheduler — systemd timers locally, or a queue-based scheduler in production. Cron is best for simple, independent, idempotent work.