Home โบ Apache Airflow โบ On the first Monday of every month at 9:00 AM
Apache Airflow cron expression: on the first Monday of every month at 9:00 AM
To run a Apache Airflow job on the first Monday of every month at 9:00 AM, use:
0 9 * * MON#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 |
|---|---|
| Apache Airflow (this page) | 0 9 * * MON#1 |
| Quartz | 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 |
| 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 Apache Airflow config
Drop this into your project. The expression is the one above.
from datetime import datetime
from airflow import DAG
from airflow.operators.empty import EmptyOperator
with DAG(
dag_id="my_dag",
start_date=datetime(2026, 1, 1),
schedule="0 9 * * MON#1", # schedule_interval= before Airflow 2.4
catchup=False,
):
EmptyOperator(task_id="start")The Apache Airflow fields, in order: minute (0-59), hour (0-23), day-of-month (1-31), month (1-12), day-of-week (0-7, 0 and 7 = Sunday).
Things to watch out for in Apache Airflow
- Weekdays are 0-6 with Sunday as 0, or names such as MON-FRI.
- croniter, which Airflow uses, extends cron with L (last day of month), W and # (nth weekday, such as MON#1). The Airflow docs show 0 0 * * MON#1.
- Airflow defaults to UTC. On a time-zone-aware DAG a cron schedule follows wall-clock time, so a daily 00:00 US/Eastern run moves between 04:00 and 05:00 UTC across daylight saving changes.
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 Apache Airflow job on the first Monday of every month at 9:00 AM?
Use 0 9 * * MON#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?
Quartz: 0 0 9 ? * 2#1; Spring: 0 0 9 * * MON#1; Crontab: 0 9 * * 1. The table on this page lists every dialect.
Which time zone does Apache Airflow use for this schedule?
Airflow defaults to UTC. On a time-zone-aware DAG a cron schedule follows wall-clock time, so a daily 00:00 US/Eastern run moves between 04:00 and 05:00 UTC across daylight saving changes.