Home โบ Quartz โบ On the first Monday of every month at 9:00 AM
Quartz cron expression: on the first Monday of every month at 9:00 AM
To run a Quartz job on the first Monday of every month at 9:00 AM, use:
0 0 9 ? * 2#1At 09:00 UTC, on the 1st Mon.
Your week at a glance
Upcoming runs
| # | Local | UTC | From now |
|---|
Copy-ready code
Why use this schedule
A monthly meeting or review that always lands on the first Monday. Calendars make this easy, but cron has no plain "first Monday" rule, so how you express it depends on the system.
- Monthly planning reports
- First-Monday-of-the-month reminders
- Monthly access reviews
First runs, as an example
Starting from 1 January 2027, evaluated in UTC:
| # | Date and time (UTC) |
|---|---|
| 1 | Mon, 04 Jan 2027, 09:00:00 |
| 2 | Mon, 01 Feb 2027, 09:00:00 |
| 3 | Mon, 01 Mar 2027, 09:00:00 |
| 4 | Mon, 05 Apr 2027, 09:00:00 |
| 5 | Mon, 03 May 2027, 09:00:00 |
| 6 | Mon, 07 Jun 2027, 09:00:00 |
On the first Monday of every month at 9:00 AM in every dialect
| System | Expression |
|---|---|
| Quartz (this page) | 0 0 9 ? * 2#1 |
| Spring | 0 0 9 * * MON#1 |
| Crontab | 0 9 * * 1 |
| Kubernetes | 0 9 * * 1 |
| AWS EventBridge | 0 9 ? * 2#1 * |
| Jenkins | H 9 * * 1 |
| GitHub Actions | 0 9 * * 1 |
| node-cron | 0 9 1-7 * 1 |
| Apache Airflow | 0 9 * * MON#1 |
| Azure Functions | 0 0 9 * * 1 |
| Google Cloud Scheduler | 0 9 * * 1 |
Need to translate a different expression? Use the cron converter.
Ready-to-use Quartz config
Drop this into your project. The expression is the one above.
Trigger trigger = TriggerBuilder.newTrigger()
.withIdentity("myTrigger", "group1")
.withSchedule(CronScheduleBuilder.cronSchedule("0 0 9 ? * 2#1")
.inTimeZone(TimeZone.getTimeZone("UTC")))
.build();The Quartz fields, in order: second (0-59), minute (0-59), hour (0-23), day-of-month (1-31), month (1-12), day-of-week (1-7, 1 = Sunday), year (1970-2199, optional).
Things to watch out for in Quartz
- Weekdays are 1-7 with Sunday as 1. Monday to Friday is 2-6, or write MON-FRI to avoid the off-by-one trap.
- L, W and # are Quartz extensions. They exist in Spring and EventBridge too, but not in Unix cron or Kubernetes.
- Quartz uses the JVM default time zone unless you set one: CronScheduleBuilder.cronSchedule(expr).inTimeZone(TimeZone.getTimeZone("UTC")).
The common mistake with this schedule
Writing 0 9 1-7 * 1 in classic cron does not mean "first Monday". Cron ORs the two day fields, so it fires on days 1-7 and every Monday. Use a guard in the script instead.
Frequently asked questions
How do I run a Quartz job on the first Monday of every month at 9:00 AM?
Use 0 0 9 ? * 2#1. At 09:00 UTC, on the 1st Mon.
What is the on the first Monday of every month at 9:00 AM cron expression in other systems?
Spring: 0 0 9 * * MON#1; Crontab: 0 9 * * 1; Kubernetes: 0 9 * * 1. The table on this page lists every dialect.
Which time zone does Quartz use for this schedule?
Quartz uses the JVM default time zone unless you set one: CronScheduleBuilder.cronSchedule(expr).inTimeZone(TimeZone.getTimeZone("UTC")).