Demystifying Crontab Syntax: A Developer's Guide to Scheduled Jobs & Automation
Comprehensive breakdown of 5-part and 6-part cron syntax, step values, timezone pitfalls, and idempotent cron script architecture.
1. The 5-Part Cron Standard
Cron is the timeless standard for automating recurring tasks in Linux servers, container clusters, and serverless workflows.
A standard cron expression consists of 5 fields separated by spaces: Minute (0-59), Hour (0-23), Day of Month (1-31), Month (1-12 or JAN-DEC), and Day of Week (0-6 or SUN-SAT).
2. Understanding Special Characters (*, /, -, ,)
Mastering cron requires understanding its four core operators:
• Asterisk (`*`): Matches every possible value in that field.
• Comma (`,`): Specifies a list of explicit values (e.g., `1,15,30`).
• Hyphen (`-`): Defines an inclusive range (e.g., `1-5` for weekdays).
• Slash (`/`): Specifies step increments (e.g., `*/15` in minutes evaluates every 15 minutes).
# Every 15 minutes during business hours (9am - 5pm, Mon - Fri)
*/15 9-17 * * 1-5 /usr/local/bin/sync-inventory.sh
# Midnight on the 1st and 15th of every month
0 0 1,15 * * /usr/local/bin/generate-payroll.sh
# Every Sunday morning at 03:30 AM
30 3 * * 0 /usr/local/bin/cleanup-archive.sh
# Every 6 hours at minute 0
0 */6 * * * /usr/local/bin/vacuum-database.sh3. Timezones and Overlapping Executions
Two common issues plague production cron systems: Daylight Saving Time shifts and task overlapping.
If a script configured to run every 5 minutes (`*/5 * * * *`) takes 7 minutes to execute due to unexpected database load, a second instance will start while the first is still running, leading to race conditions.
Always wrap cron commands with lock mechanisms like `flock` or Redis distributed locks to enforce single-instance execution.