Question 1

What is a cron expression?

Accepted Answer

A cron expression is a string of five or six fields separated by spaces that defines when a scheduled task should run. Each field represents a unit of time: minute, hour, day of month, month, and day of week. For example, 0 9 * * MON-FRI runs a job at 9:00 AM every weekday. Cron expressions are used in Unix/Linux systems, cloud schedulers, and job queues to automate recurring tasks without manual intervention.

Question 2

What is the difference between Standard (5-field) and Quartz (6-field) cron?

Accepted Answer

Standard cron uses five fields: minute, hour, day of month, month, and day of week. Quartz cron, used by Java-based schedulers like Spring and Quartz Scheduler, adds a seconds field at the beginning, making it six fields total. For example, the Standard expression 0 9 * * * becomes 0 0 9 * * * in Quartz. Use Standard for Unix/Linux crontab and most cloud platforms; use Quartz if your application explicitly requires it.

Question 3

How do I run a cron job every 5, 10, or 15 minutes?

Accepted Answer

Use the step operator (/) in the minute field. */5 * * * * runs every 5 minutes, */10 * * * * runs every 10 minutes, and */15 * * * * runs every 15 minutes. The * means every possible value and /n means every nth value. You can combine this with a range — for example 0-30/5 * * * * runs every 5 minutes but only within the first 30 minutes of each hour.

Question 4

How do I schedule a cron job to run at a specific time every day?

Accepted Answer

Set the minute and hour fields to fixed values and use * for the rest. For example, 30 14 * * * runs every day at 2:30 PM. To run at midnight use 0 0 * * *, and for noon use 0 12 * * *. To restrict it to weekdays only, replace the last * with MON-FRI, giving you 30 14 * * MON-FRI.

Question 5

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

Accepted Answer

Each character has a specific role. The asterisk (*) means every possible value for that field. The slash (/) defines a step interval — */5 means every 5 units. The hyphen (-) defines a range — MON-FRI means Monday through Friday. The comma (,) separates a list of specific values — 1,15 in the day field means the 1st and 15th of the month. Combining these lets you build precise schedules like */15 9-17 * * MON-FRI, which means every 15 minutes during business hours on weekdays.

Question 6

What are non-standard cron operators like L, W, and #?

Accepted Answer

These operators are supported in Quartz and some extended cron implementations but not in standard Unix crontab. L means last — L in the day-of-month field means the last day of the month. W means nearest weekday — 15W runs on the nearest weekday to the 15th. # means the nth occurrence of a weekday — MON#2 means the second Monday of the month. L-n means n days before the last day — L-3 means 3 days before month end. Always check whether your scheduler supports these before using them.

Question 7

How do I run a cron job on the first or last day of every month?

Accepted Answer

To run on the first day of every month, use 0 0 1 * * which triggers at midnight on the 1st. To run on the last day of the month, use the L operator if your scheduler supports it: 0 0 L * *. If you are using standard Unix cron which does not support L, a common workaround is to check inside your script whether tomorrow is the 1st of the next month.

Question 8

How do I validate a cron expression to make sure it is correct?

Accepted Answer

This tool validates your expression in real time as you type. A green banner shows the plain-English description of your schedule, and the Next run section shows the exact upcoming dates. If the expression is invalid, the banner turns red with an error message. You can also cross-check by switching between Standard and Quartz format — if the field count does not match the selected format, the expression will show as invalid.

Question 9

Why is my cron job not running at the expected time?

Accepted Answer

The most common reasons are timezone differences, incorrect field order, and environment path issues. Cron runs in UTC by default on many servers, so a job set to run at 9 AM may run at a different local time. Make sure your expression uses the correct field order: minute, hour, day of month, month, day of week. Also ensure the script path is absolute — cron has a limited environment and does not inherit your shell's PATH. Use the Next run preview in this tool to verify the exact times before deploying.

Question 10

Can I use this cron expression generator for AWS, GCP, or other cloud schedulers?

Accepted Answer

Yes. Most cloud schedulers use standard 5-field cron syntax. AWS EventBridge uses a slightly modified syntax closer to Quartz with 6 fields and supports the ? operator for day fields. Google Cloud Scheduler uses standard 5-field Unix cron. Azure Logic Apps and Functions support both formats. Generate your expression here, verify the next run dates match your expectation, and paste it into your cloud scheduler's schedule field.

Part	Value	Explanation
Minute	`*`	Any value
Hour	`*`	Any value
Day (Month)	`*`	Any value
Month	`*`	Any value
Day (Week)	`5`	Only on Friday

Operator	Description	Example
*	Any value (wildcard)	* in minute field = every minute
,	Value list separator	1,15 in day field = 1st and 15th day
-	Range of values	1-5 in weekday field = Monday to Friday
/	Step values	*/15 in minute field = every 15 minutes
0-6 (7)	Day of week (0 and 7 are Sunday)	1-6 = Monday to Saturday
1-12	Month (1 is January)	1 = January
1-31	Day of month	15 = 15th day of month
0-23	Hour (24-hour format)	0 = midnight, 12 = noon
0-59	Minute	30 = 30 minutes past the hour
MON-SUN	Day name abbreviations	MON = Monday
JAN-DEC	Month name abbreviations	JAN = January

Operator	Description	Example
?	No specific value (used in day-of-month or day-of-week)	0 0 ? * MON = Run at midnight every Monday
L	Last day of period	0 0 L * * = Run at midnight on the last day of the month
W	Nearest weekday	0 0 15W * * = Run at midnight on the nearest weekday to the 15th
#	Nth occurrence of a weekday in the month	0 0 * * MON#3 = Run at midnight on the third Monday of the month
L-n	n days before the last day of the month	0 0 L-3 * * = Run at midnight 3 days before the last day of the month

Cron Expression Generator

Expression breakdown

Cron operators

Non-standard operators

Frequently asked questions about cron expressions