How to Write and Debug Cron Expressions: The Complete Crontab Guide

Automation is the backbone of modern software infrastructure. Whether scheduling database backups, generating nightly analytics rollups, or firing recurring email newsletters, Unix-based systems and cloud orchestrators (like Kubernetes, AWS EventBridge, and GitHub Actions) rely on cron expressions.

Despite its brevity, standard cron syntax can be notoriously difficult to read at a glance, leading to accidental misconfigurations like firing heavy jobs every minute instead of once per hour.

The Standard 5-Field Cron Structure

A traditional Unix cron expression consists of five space-separated fields representing specific units of time:

┌───────────── minute (0 - 59)
│ ┌───────────── hour (0 - 23)
│ │ ┌───────────── day of the month (1 - 31)
│ │ │ ┌───────────── month (1 - 12 or JAN - DEC)
│ │ │ │ ┌───────────── day of the week (0 - 6 or SUN - SAT)
│ │ │ │ │
* * * * *

Essential Operators You Need to Know

1. The Asterisk (*): Represents "every possible value." An asterisk in the minute field means the task executes every single minute.
2. The Comma (,): Specifies a discrete list of values. For example, 15,45 * * * * executes at minutes 15 and 45 of each hour.
3. The Hyphen (-): Defines an inclusive numerical range. For instance, 0 9-17 * * 1-5 runs at minute 0 of every hour between 9:00 AM and 5:00 PM, Monday through Friday.
4. The Slash (/): Denotes step increments. */15 * * * * executes every 15 minutes (at :00, :15, :30, and :45).

Common Scheduling Recipes

Here are the most widely used scheduling patterns in production environments:

• Every minute: * * * * *
• Top of every hour: 0 * * * *
• Daily at midnight: 0 0 * * *
• Every Sunday at 3:00 AM: 0 3 * * 0
• First day of each month at 06:00 AM: 0 6 1 * *
• Every 10 minutes during working hours: */10 9-17 * * 1-5

Avoiding Production Traps

A frequent pitfall occurs when configuring both day of the month and day of the week. In standard cron implementations, if both fields are specified (not *), the schedule triggers when either condition matches (OR logic, not AND logic).

To build, verify, and translate your schedule strings without risking production downtime, use our free Cron Expression Builder & Generator. It provides visual field selectors, plain-English explanations, and live previews of the next upcoming execution timestamps.