Imagine setting up a database backup to run every night at 2 AM — and then discovering a week later that it was actually running every two minutes because of a typo in your cron expression. Logs filled up, disk space was gone, and the server crawled to a halt.
This kind of story is more common than you'd think. Cron expressions are powerful, but their syntax is compact enough that a single misplaced character can produce wildly unexpected behavior.
This guide walks you through how cron scheduling works, shows you the most common patterns, and explains how to validate your expressions before you point them at anything important.
1. Understanding the 5-Field Cron Syntax
A cron expression is just a string of five fields, separated by spaces. Each field controls a different unit of time:
┌───────────── minute (0 - 59)
│ ┌─────────── hour (0 - 23)
│ │ ┌───────── day of month (1 - 31)
│ │ │ ┌─────── month (1 - 12)
│ │ │ │ ┌───── day of week (0 - 6, Sunday = 0)
│ │ │ │ │
* * * * *
The Four Core Symbols
*(asterisk) — "every." An asterisk in the minute field means "every minute.",(comma) — "and these specific values."1,15,30in the minute field means "at minute 1, 15, and 30."-(hyphen) — "a range."1-5in the day-of-week field means "Monday through Friday."/(slash) — "every N."*/10in the minute field means "every 10 minutes."
2. Build and Validate Your Expression Before Running It
Writing cron expressions by hand is fine once you know the syntax well. But for anything you're about to run on a production server, it's worth verifying your expression first — ideally in a visual tool that shows you a plain-English explanation of what it does.
Cron Expression Builder
Visual cron expression editor that translates cron syntax into plain English.
Security Note: Keep Infrastructure Details Private
Cron schedules aren't just timing information — they can reveal a lot about how your infrastructure is organized. Backup frequencies, maintenance windows, and script paths all tell a story about your system architecture.
For this reason, it's worth thinking twice before pasting your cron configuration into a public or cloud-dependent tool:
- In regulated tech environments (financial services, healthcare): Security standards in the US (SOC 2, HIPAA) and Europe (ISO 27001, UK Cyber Essentials) require that infrastructure configuration details stay within authorized systems.
- In Silicon Valley and London tech firms: NDA agreements with clients often extend to internal tooling and infrastructure schedules.
- In India's growing tech sector: DPDP Act guidelines around data localization support keeping configuration details within controlled environments.
The Cron Builder on FluxToolkit runs entirely in your browser. No cron expressions or script paths are sent to any server.
3. Common Cron Patterns You'll Actually Use
| Schedule | Expression | What it does |
|---|---|---|
| Every minute | * * * * * |
Runs at the start of every minute |
| Every 15 minutes | */15 * * * * |
Runs at :00, :15, :30, :45 |
| Daily at midnight | 0 0 * * * |
Runs once per day at 00:00 |
| Every Sunday at midnight | 0 0 * * 0 |
Weekly job on Sundays |
| Weekdays, 9am–5pm hourly | 0 9-17 * * 1-5 |
Business hours automation |
4. Setting Up a Cron Job on Linux
# Open your user's crontab for editing
crontab -e
# Add a cron line: run backup script daily at 2AM, log output
0 2 * * * /usr/local/bin/backup.sh >> /var/log/backup.log 2>&1
# List all active cron jobs for your user
crontab -l
A few important rules when writing cron commands:
- Always use absolute paths — cron runs with a minimal shell environment and may not find commands by name alone.
- Redirect output to a log file — otherwise you'll never know if something failed.
- Test the script manually first before scheduling it.
Frequently Asked Questions
What is a cron job?
A cron job is a task that runs automatically on a schedule in Unix-like operating systems (Linux, macOS). It's defined by a cron expression that specifies exactly when the job should run.
What's the difference between 5-field and 6-field cron expressions?
Standard Unix cron uses 5 fields (minute, hour, day, month, weekday). Some platforms like AWS EventBridge or Quartz Scheduler add a 6th field for seconds — giving you more precise control over timing.
My cron job isn't running. How do I troubleshoot it?
Check three things: (1) Is the cron daemon running? (systemctl status cron). (2) Does your script have execute permissions? (chmod +x script.sh). (3) Are you using absolute file paths for everything in the script?
Does FluxToolkit log my cron expressions?
No. The Cron Builder runs entirely in your browser. Nothing you type is sent to our servers.
Related Articles
A Complete Guide to Decoding JWT Tokens — Automated jobs often use JWT tokens for scheduled API authentication.
SQL Formatting: Why It Matters — Scheduled database maintenance jobs need clean, readable SQL.
Strong Passwords and Cryptographic Hashes — Protect the scripts your cron jobs execute.
Unix Timestamp Converter — Cron jobs run at specific times — understand Unix timestamps to debug schedules.
JSON vs XML vs YAML vs CSV — Cron jobs are often configured in YAML (GitHub Actions, CI/CD pipelines).