Cron & Airflow Schedule Builder
When does this cron expression actually run? Enter a cron expression or an Airflow preset to get its next run times, a plain-language description, and the Airflow-specific behaviour (catchup, backfill, UTC) that trips people up.
- Free with a free account
- Runs on our server in milliseconds
- Your input is not stored or logged
Create a free account to use the builder
Members use every tool on AIDataLegends for free. It takes a name, an email and a password, and you come straight back here.
Not ready yet? The worked example below shows exactly what the tool produces.
Worked example
The expression 0 9 * * 1-5 — a common Airflow DAG schedule meaning 09:00 on
weekdays — computed from 1 January 2026. The builder's answer:
Runs at 09:00, only on Monday, Tuesday, Wednesday, Thursday and Friday.
Expression: 0 9 * * 1-5
| # | Date | Time (UTC) | Day |
|---|---|---|---|
| 1 | 2026-01-01 | 09:00 | Thursday |
| 2 | 2026-01-02 | 09:00 | Friday |
| 3 | 2026-01-05 | 09:00 | Monday |
| 4 | 2026-01-06 | 09:00 | Tuesday |
| 5 | 2026-01-07 | 09:00 | Wednesday |
What this means
- In Airflow, this is the DAG's schedule_interval/schedule. Airflow runs a scheduled DAG at the END of the interval: the run labelled for a given date covers the period ending then (data_interval_start/data_interval_end), not the moment it starts. With catchup=True (the default), Airflow backfills every missed interval since the DAG's start_date the first time it's turned on -- set catchup=False if you only want future runs.
- Times here are naive clock time with no timezone applied -- this matches an Airflow DAG with no explicit timezone set, which runs in UTC.
The five fields
A standard cron expression (the kind Airflow's schedule/schedule_interval accepts)
has five space-separated fields, in this order:
| Field | Allowed values | Special characters |
|---|---|---|
| Minute | 0–59 | * any value, , a list,
- a range, / a step (e.g. */15) |
| Hour | 0–23 | |
| Day of month | 1–31 | |
| Month | 1–12 or JAN–DEC | |
| Day of week | 0–6 (0 = Sunday) or SUN–SAT |
Airflow also accepts the shorthand presets @hourly, @daily, @weekly,
@monthly and @yearly in place of a 5-field expression — this builder expands them the
same way Airflow does before computing anything.
The rule almost everyone gets wrong: day-of-month OR day-of-week
When both day-of-month and day-of-week are restricted (neither is *), standard
cron — and Airflow's scheduler, which uses the same semantics — runs on a date that matches
either field, not both. 0 9 1 * 1 doesn't mean "the first Monday of the month";
it means "the 1st of the month, and every Monday", which is usually not what was intended. If you only
want one of the two conditions, leave the other field as *.
How this maps to an Airflow DAG
- The schedule is the interval, not just a trigger time. Airflow labels a scheduled run by
the start of the period it covers (
data_interval_start) and actually executes it once that period ends (data_interval_end). A@dailyDAG's "2026-01-01" run executes at the end of January 1st, with data up to that point — not at the start of the day. catchupdefaults toTrue. The first time a DAG is turned on, Airflow schedules a run for every interval between itsstart_dateand now, unlesscatchup=Falseis set. A schedule that "only just started lagging" is almost always this.- No timezone means UTC. A DAG with no explicit
timezone=argument runs on UTC wall-clock time, same as this builder's results. Set aTimezoneon the DAG to schedule by local time (and to handle daylight-saving changes, which this tool does not model).
Limitations and assumptions
- Only the standard 5-field format is supported. Six-field crons with a leading seconds column (used by some non-cron schedulers) are not.
- Times are naive clock time with no timezone or daylight-saving handling — correct for UTC, which is Airflow's default, but not for a DAG with a local timezone set.
- The description covers common schedule shapes in plain language; unusual combinations fall back to a literal field-by-field readout rather than a guessed English sentence.