Cron Expressions & Crontab Syntax

Cron is a time-based daemon and job scheduling utility native to Unix-like operating systems, originally created by Brian Kernighan. Automated tasks—known as cron jobs—are scheduled through crontab (cron table) configuration files using 5-field (standard POSIX) or 6-field (extended quartz) cron expressions. Cron expressions dictate recurring automation intervals for database backups, cache invalidations, report generation, and system maintenance.

Parse, test, and generate human-readable schedules with our interactive Cron Expression Parser & Schedule Generator.

---

Technical Specifications at a Glance

Property	Standard POSIX Cron	Quartz / Extended Cron
Field Count	5 fields	6 or 7 fields (includes Seconds & Year)
Resolution	1 Minute	1 Second
Configuration File	/etc/crontab or crontab -e	Framework config (Spring, Node-Cron, AWS EventBridge)
Special Nicknames	@reboot, @daily, @hourly, @weekly	@yearly, @monthly, @midnight
Timezone Sensitivity	System local time or UTC (CRON_TZ)	Configurable per expression or cluster
Execution User	Defined in crontab or per system user	Execution context / IAM role

---

Understanding the 5-Field Standard Cron Expression

A standard POSIX cron expression consists of five whitespace-delimited fields representing consecutive units of time:

┌───────────── Minute (0 - 59)
│ ┌─────────── Hour (0 - 23)
│ │ ┌───────── Day of Month (1 - 31)
│ │ │ ┌─────── Month (1 - 12 or JAN - DEC)
│ │ │ │ ┌───── Day of Week (0 - 6 or SUN - SAT, 0 is Sunday)
│ │ │ │ │
* * * * *

Supported Special Characters

Symbol	Name	Description	Example
*	Wildcard (Asterisk)	Matches all possible values in that field.	* * * * * (Every minute)
,	Value List (Comma)	Specifies a discrete list of values.	0 9,17 * * * (At 09:00 and 17:00)
-	Range (Hyphen)	Defines an inclusive range of values.	0 9-17 * * * (Every hour from 9 AM to 5 PM)
/	Step Values (Slash)	Specifies increments within a range or wildcard.	*/15 * * * * (Every 15 minutes)
?	No Specific Value	Used in extended/Quartz cron for day-of-month or day-of-week.	0 0 12 ? * MON-FRI

---

Common Real-World Cron Examples

# Run every 5 minutes
*/5 * * * * /usr/local/bin/healthcheck.sh

# Run at midnight every Sunday
0 0 * * 0 /opt/scripts/backup-db.sh

# Run at 08:30 on the 1st of every month
30 8 1 * * /usr/bin/python3 /app/generate_invoices.py

# Run every weekday at 09:00 UTC
0 9 * * 1-5 /app/notify_standup.sh

---

Code Examples: Scheduling Tasks

Modern JavaScript (Node.js using node-cron)

import cron from 'node-cron';

// Schedule a background sync every 10 minutes
const task = cron.schedule('*/10 * * * *', async () => {
  const timestamp = new Date().toISOString();
  console.log(`[${timestamp}] Running scheduled cache cleanup...`);
  await performCachePurge();
}, {
  scheduled: true,
  timezone: 'UTC'
});

async function performCachePurge() {
  // Purge expired Redis keys
}

Python (using APScheduler or crontab helper)

from apscheduler.schedulers.blocking import BlockingScheduler

scheduler = BlockingScheduler(timezone="UTC")

# Run everyday at 04:00 AM UTC
@scheduler.scheduled_job('cron', hour=4, minute=0)
def daily_maintenance():
    print("Executing automated database vacuum and reindexing...")

if __name__ == '__main__':
    scheduler.start()

---

Common Pitfalls & Best Practices

1. Environment Variables Missing: Cron jobs execute with a minimal shell environment (/usr/bin:/bin). Commands relying on custom $PATH, .env variables, or runtime managers like nvm or pyenv will fail unless explicitly sourced in the crontab wrapper.
2. Overlapping Job Runs: Long-running jobs scheduled frequently (e.g., every minute) may overlap and exhaust system resources. Use lock files (flock on Linux) to prevent concurrent execution:

   * * * * * /usr/bin/flock -n /var/lock/sync.lock /usr/local/bin/sync-data.sh
   

3. Timezone Pitfalls & Daylight Saving Time (DST): Relying on local server time causes jobs scheduled between 02:00 and 03:00 to run twice or get skipped during daylight saving transitions. Always configure servers and cron jobs to operate in UTC.

---

Frequently Asked Questions

What happens if both day-of-month and day-of-week are specified?

In standard POSIX cron, if both the day-of-month (field 3) and day-of-week (field 5) fields are non-wildcard values, they operate with a logical OR relationship. The job will execute when either condition evaluates to true, not when both match.

What is the difference between crontab and systemd timers?

While traditional crontab is simple to configure, modern Linux distributions frequently adopt systemd timers. Systemd timers offer millisecond precision, integrated logging via journalctl, dependency chains between services, and graceful failure handling.

How can I convert a cron schedule to plain English?

Reading complex patterns like 23 0-20/2 * * * manually is error-prone. Use our free Cron Parser Tool to inspect human descriptions, next trigger timestamps, and cron intervals instantly.