Home โบ Apache Airflow โบ Every minute
Apache Airflow cron expression: every minute
To run a Apache Airflow job every minute, use:
* * * * *Every minute.
Your week at a glance
Upcoming runs
| # | Local | UTC | From now |
|---|
Copy-ready code
Why use this schedule
The fastest schedule most cron systems allow. It suits near-real-time polling where waiting five minutes is too slow.
- Polling a queue or an inbox for new work
- Heartbeat pings to an uptime monitor
- Flushing a small in-memory buffer to disk
First runs, as an example
Starting from 1 January 2027, evaluated in UTC:
| # | Date and time (UTC) |
|---|---|
| 1 | Fri, 01 Jan 2027, 00:00:00 |
| 2 | Fri, 01 Jan 2027, 00:01:00 |
| 3 | Fri, 01 Jan 2027, 00:02:00 |
| 4 | Fri, 01 Jan 2027, 00:03:00 |
| 5 | Fri, 01 Jan 2027, 00:04:00 |
| 6 | Fri, 01 Jan 2027, 00:05:00 |
Every minute in every dialect
| System | Expression |
|---|---|
| Apache Airflow (this page) | * * * * * |
| Quartz | 0 * * * * ? |
| Spring | 0 * * * * * |
| Crontab | * * * * * |
| Kubernetes | * * * * * |
| AWS EventBridge | * * * * ? * |
| Jenkins | * * * * * |
| node-cron | * * * * * |
| Azure Functions | 0 * * * * * |
| Google Cloud Scheduler | * * * * * |
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="* * * * *", # 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
- Airflow parses cron with croniter, so */15 means :00, :15, :30 and :45. Presets such as @hourly and @daily are accepted too.
- 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
A job that takes longer than one minute will overlap with the next run. Guard against it with a lock, Quartz @DisallowConcurrentExecution, or concurrencyPolicy: Forbid in Kubernetes.
Frequently asked questions
How do I run a Apache Airflow job every minute?
Use * * * * *. Every minute.
What is the every minute cron expression in other systems?
Quartz: 0 * * * * ?; Spring: 0 * * * * *; Crontab: * * * * *. 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.