Question 1

Why should I validate cron expressions before deploying?

Accepted Answer

An invalid cron expression can silently fail or run at unexpected times, causing missed backups, billing anomalies, or server outages. Validating before deployment catches syntax errors that won't be obvious until a job fires at the wrong time.

Question 2

What is the difference between 5-field and 6-field cron?

Accepted Answer

Standard 5-field cron is: minute hour day-of-month month day-of-week. 6-field cron (used by Spring @Scheduled and some cloud schedulers) prepends a seconds field: second minute hour day-of-month month day-of-week.

Question 3

What do the special characters * / - , mean in cron?

Accepted Answer

* matches any value. / defines a step (*/15 = every 15 units). - defines a range (1-5 = values 1 through 5). , defines a list (1,3,5 = each of those specific values).

Question 4

Can I use month names or weekday names in cron?

Accepted Answer

Some cron implementations support names like JAN-DEC for months and SUN-SAT for weekdays. However, numeric values (1-12 for months, 0-7 for weekdays where both 0 and 7 = Sunday) are universally supported across all platforms.

Question 5

What happens if both DOM and DOW are specified?

Accepted Answer

When both day-of-month and day-of-week contain non-wildcard values, most cron implementations (Vixie cron) use OR logic — the job runs when either condition is true. For strict AND behavior, use a wrapper script that checks both conditions.

Question 6

Are L and W characters supported in standard cron?

Accepted Answer

L (last day) and W (nearest weekday) are Quartz Scheduler and Spring @Scheduled extensions. They are NOT supported by standard Linux crontab. AWS EventBridge has its own special characters. Always check your platform's documentation.

Question 7

How does cron differ between AWS EventBridge and GitHub Actions?

Accepted Answer

AWS EventBridge uses 6-field cron (with seconds) and requires non-wildcard values in either DOM or DOW (not both). GitHub Actions uses standard 5-field cron in UTC timezone with a minimum interval of approximately 5 minutes for scheduled workflows.

Question 8

How can I test a cron expression without running it on a server?

Accepted Answer

Use an online cron validator or parser (like this tool) to check the syntax and calculate next run times. Tools like cron-parser npm package or the croniter Python library let you calculate next runs programmatically before deploying.

Cron Validator