Cron Expression Complete Guide - Schedule Tasks Like a Pro

What is a Cron Expression?

A Cron expression is a string format used to define schedules for recurring tasks in Unix-like systems, job schedulers, and cloud platforms. Understanding cron syntax is essential for automating tasks, backups, reports, and maintenance jobs.

Cron Expression Syntax

A standard cron expression consists of 5 or 6 fields separated by spaces:

  * * * * * *
    │ │ │ │ │ │
    │ │ │ │ │ └─ Day of week (0-7) (0 or 7 = Sunday)
    │ │ │ │ └─── Month (1-12)
    │ │ │ └───── Day of month (1-31)
    │ │ └─────── Hour (0-23)
    │ └───────── Minute (0-59)
    └─────────── Second (0-59) [Optional in some systems]

Special Characters in Cron

• * - Matches any value (wildcard)
• , - List separator (e.g., 1,3,5)
• - - Range (e.g., 1-5)
• / - Step values (e.g., */5 = every 5 units)
• ? - No specific value (day-of-month or day-of-week only)
• L - Last (e.g., L in day = last day of month)
• W - Nearest weekday
• # - Nth occurrence (e.g., 2#1 = first Monday)

Common Cron Expression Examples

Every Minute

  * * * * *
    Runs: Every minute, every hour, every day

Every Hour

  0 * * * *
    Runs: At minute 0 of every hour (12:00, 1:00, 2:00...)

Every Day at Midnight

  0 0 * * *
    Runs: Daily at 00:00 (midnight)

Every Monday at 9 AM

  0 9 * * 1
    Runs: Every Monday at 09:00

First Day of Every Month

  0 0 1 * *
    Runs: At midnight on the 1st day of every month

Every 15 Minutes

  */15 * * * *
    Runs: At minutes 0, 15, 30, 45 of every hour

Every Weekday at 6 PM

  0 18 * * 1-5
    Runs: Monday through Friday at 18:00

Every 5 Hours

  0 */5 * * *
    Runs: At minute 0 past every 5th hour (00:00, 05:00, 10:00...)

Advanced Cron Examples

Last Day of Month at Noon

  0 12 L * *
    Runs: At 12:00 on the last day of every month

First Monday of Every Month

  0 0 * * 1#1
    Runs: At midnight on the first Monday of every month

Business Hours Only

  0 9-17 * * 1-5
    Runs: Every hour from 9 AM to 5 PM, Monday through Friday

Quarterly Reports

  0 0 1 1,4,7,10 *
    Runs: At midnight on Jan 1, Apr 1, Jul 1, Oct 1

Day of Week Values

Month Values

Months can be specified as numbers (1-12) or names (JAN-DEC):

  0 0 1 1 *      # January 1st at midnight (numeric)
    0 0 1 JAN *    # January 1st at midnight (name)
    0 0 15 6,12 *  # 15th of June and December

Common Use Cases

System Administration

• Backups - 0 2 * * * (Daily at 2 AM)
• Log Rotation - 0 0 * * 0 (Weekly on Sunday)
• System Updates - 0 3 * * 1 (Monday at 3 AM)
• Disk Cleanup - 0 4 1 * * (First of month at 4 AM)

Web Applications

• Send Reports - 0 8 * * 1 (Monday mornings)
• Database Optimization - 0 3 * * 0 (Sunday night)
• Cache Clearing - */30 * * * * (Every 30 minutes)
• Email Digests - 0 17 * * 5 (Friday at 5 PM)

Data Processing

• ETL Jobs - 0 1 * * * (Daily at 1 AM)
• Data Sync - */15 * * * * (Every 15 minutes)
• Report Generation - 0 0 1 * * (Monthly reports)

Cron Expression Testing Tips

1. Use Online Tools - Test expressions before deployment
2. Check Timezone - Ensure server timezone matches expectations
3. Consider Overlap - Long-running jobs may overlap with next execution
4. Log Execution - Monitor job execution and failures
5. Handle Edge Cases - Test end-of-month, leap years, DST changes

Cron vs Other Schedulers

Cron (Unix/Linux)

• Built into Unix/Linux systems
• Lightweight and efficient
• Simple for basic scheduling
• Limited error handling
• No built-in retry logic

Task Scheduler (Windows)

• GUI interface
• Advanced triggers and conditions
• Better error reporting
• Windows-specific

Cloud Schedulers (AWS EventBridge, GCP Cloud Scheduler)

• Highly available and scalable
• Integrated with cloud services
• Monitoring and alerting
• Additional cost
• Platform-specific

Best Practices

1. Avoid Overlap - Ensure jobs complete before next execution
2. Use Locking - Prevent multiple instances running simultaneously
3. Error Handling - Log failures and send alerts
4. Resource Management - Schedule intensive tasks during off-peak hours
5. Documentation - Comment cron entries with descriptions
6. Monitoring - Track execution success/failure rates

Try Our Cron Parser

Validate and understand your cron expressions with our free online parser:

Quick Reference Table