About the Cron Expression Builder
The Cron Expression Builder & Decoder works in both directions: build a schedule visually via the five-field UI (minute / hour / day-of-month / month / day-of-week, with asterisks, ranges, lists, and step values), or paste an existing expression like 0 9 * * 1-5 to decode it into plain English. Every result surfaces the next 10 execution times and a weekly heatmap so you can spot accidental clustering before deploying.
It is built for sysadmins setting up backup jobs at 3 AM, DevOps engineers wiring up Kubernetes CronJobs and GitHub Actions schedules, data engineers automating ETL pipelines, developers configuring Laravel scheduler / Rails whenever / Celery Beat, and anyone who has ever written 0 0 1 * 1 intending “midnight on the first Monday” and accidentally created a job that fires both on the 1st AND every Monday.
All parsing and rendering runs in JavaScript on your device. Expressions, preset selections, and next-execution previews never leave your browser — the page makes no network call after first load. Cron strings can encode internal scheduling logic and operational windows; the tool treats them accordingly by never seeing them.
Cron implementations diverge. Standard Unix cron (Vixie cron) resolves to minutes; Quartz (Java) adds a seconds field and the L (last) / W (weekday) extensions; AWS EventBridge, GitHub Actions, and Kubernetes CronJobs default to UTC regardless of server timezone. Confirm the dialect and timezone in the runtime that will actually fire the job — an off-by-one-hour bug from DST or a misread L on a payroll job has ended more weekends than it should.
Paste multiple cron expressions (one per line) to find scheduling conflicts.
Cron Expression Syntax Explained
A cron expression consists of five fields: minute (0-59), hour (0-23), day of month (1-31), month (1-12), and day of week (0-6, where 0 is Sunday). The asterisk (*) means “every,” a comma separates multiple values, a hyphen defines a range, and a slash defines intervals (*/5 means “every 5”).
Common Cron Examples
0 9 * * 1-5 runs at 9 AM on weekdays. */15 * * * * runs
every 15 minutes. 0 0 1 * * runs at midnight on the first of every month.
30 8 * * 1 runs at 8:30 AM every Monday. These are the building blocks
for most scheduled tasks.
Cron in Different Environments
The 5-field cron format is used in Linux crontab, AWS CloudWatch Events, GitHub Actions, Kubernetes CronJobs, and many CI/CD platforms. Some systems like Quartz and Spring use a 6-field format that adds seconds as the first field. AWS EventBridge uses a 6-field format with years as the last field.
Common Cron Mistakes
The most common mistakes include confusing day-of-week numbering (0 vs 1 for Sunday), forgetting that both day-of-month and day-of-week can trigger independently, and not accounting for timezone differences between the server and your local time. Always verify your expression with the “Next 10 Execution Times” panel.
Cron in Containerized and Cloud Environments
Running cron inside Docker containers requires care because the standard cron daemon
does not start automatically and environment variables set by the container runtime
are not inherited by the cron process unless explicitly forwarded. Kubernetes offers
a first-class CronJob resource that schedules Pods on a cron expression,
handles retries, and respects concurrency policies such as Forbid or
Replace — though all expressions are evaluated in UTC by default unless
the cluster is configured otherwise. On AWS, EventBridge Scheduler and CloudWatch
Events both accept cron expressions, but EventBridge uses a 6-field format that
adds a year field and does not support the ? wildcard the same way
Quartz does. The most common cloud pitfall is writing an expression in local time
without accounting for UTC offsets, which causes jobs to fire at unexpected hours
after a daylight saving time transition.
Debugging and Monitoring Cron Jobs
Testing a cron job without waiting for the scheduled time is straightforward: set
the expression to run every minute (* * * * *), verify the output,
then restore the real schedule. Structured logging is essential — write a timestamped
entry at both the start and end of each run, including the exit code, so you can
quickly identify missed or overlapping executions in your log aggregator. A
dead man’s switch, sometimes called a heartbeat monitor, is a simple and
effective reliability pattern: the job pings an external URL on successful
completion, and the monitoring service alerts you if no ping arrives within a
defined window. Services like Healthchecks.io provide this out of the box. For
mission-critical jobs, also configure alerts on the inverse condition — triggering
when the same job runs twice in a window, which indicates a concurrency bug or
overlapping schedule.
Building reliable scheduled jobs often involves validating the data those jobs produce or consume. The Regex Tester is handy for crafting and testing patterns used inside cron-driven log parsers or file-matching scripts, while the JSON Formatter & Validator helps you inspect and validate the JSON configuration files and API payloads that your scheduled tasks frequently read and write.
Frequently Asked Questions
What does 0 */6 * * * mean in cron?
It runs at minute 0 of every sixth hour, so the job fires at 00:00, 06:00, 12:00, and 18:00 each day. The slash operator defines step values within a range, and omitting the range with just */6 is equivalent to 0-23/6 for the hour field.
What timezone does cron use?
Standard Unix cron uses the system timezone of the server, typically set via /etc/timezone or the TZ environment variable. Managed services such as AWS EventBridge, GitHub Actions, and Kubernetes CronJobs default to UTC, so always confirm the timezone before scheduling.
How do I run a cron job on the last day of the month?
Classic Unix cron does not support this directly. Most extended cron implementations like Quartz accept L for the last day of month, while Vixie cron users typically work around it by running daily and checking date -d tomorrow inside the script.
What is the difference between day-of-month and day-of-week fields?
When both fields are restricted, most cron daemons use OR logic, meaning the job runs if either field matches. The expression 0 0 1 * 1 fires on the first of the month and on every Monday, which often surprises new users.
Can cron handle seconds?
Standard Unix cron resolves only to minutes. For second-level scheduling, use Quartz, systemd timers with OnCalendar, or a job runner like Celery Beat. Polling every minute from cron and sleeping inside the script is a common but fragile workaround.
