GitHub user PrithwishDas101 deleted a comment on the discussion: schedule
interval
Not exactly! Setting `schedule_interval=None` means Airflow won't create DAG
runs automatically on a time-based schedule. You'll need to trigger the DAG
manually or through an external mechanism.
The `logical_date` belongs to each DAG run; setting `schedule_interval=None`
does not force every run to use the same logical date. A manual trigger
normally uses the trigger's default logical date unless you explicitly provide
one.
For example, if you trigger the DAG twice at different times, those runs won't
automatically share the same logical date.
One more distinction: `start_date` doesn't mean the DAG will execute at that
date when you define it. It establishes the start of the DAG's scheduling
timeline, where applicable.
Your configuration is valid for a manually triggered DAG in Airflow 2:
dag = DAG(
dag_id="04_time_delta",
start_date=dt.datetime(2026, 1, 7),
schedule_interval=None,
)
If you're using Airflow 3, the equivalent argument is `schedule=None`.
See the official docs on [[DAG runs and manual
triggering](https://airflow.apache.org/docs/apache-airflow/stable/dag-run.html)](https://airflow.apache.org/docs/apache-airflow/stable/dag-run.html)
for more details.
GitHub link:
https://github.com/apache/airflow/discussions/60198#discussioncomment-18946589
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]
