You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airflow.apache.org by Constance Martineau <co...@astronomer.io.INVALID> on 2025/03/30 18:05:42 UTC
[LAZY CONSENSUS] Clarifying logical_date behavior for manually triggered DAGs in Airflow 3
Hi all,
As part of the Airflow 3 beta process, we've received early feedback
regarding the updated behaviour of `logical_date=None` for manually
triggered DAGs as introduced in the AIP-83 amendment
<https://cwiki.apache.org/confluence/display/AIRFLOW/Option+2+clarification+doc+WIP>
.
Based on this feedback, I'd like to propose that we default the
`logical_date` to `utc.now()` for manually triggered DAGs. The change
<https://github.com/apache/airflow/issues/48412> is aimed at preserving the
current task context behaviour and minimizing disruption for DAG authors
upgrading to Airflow 3.
We've found that omitting the `logical_date` entirely causes several task
context fields to be missing, breaking common patterns and making the
upgrade more difficult than intended. This small adjustment helps us better
meet one of the key goals of Airflow 3: Smoother migration and improved UX
for DAG authors.
Because this differs slightly from the current AIP-83 amendment, I'm
bringing it to the list under lazy consensus. If no objections are raised
by 2:30pm EDT on April 2, 2025 (countdown
<https://www.timeanddate.com/countdown/generic?iso=20250402T1430&p0=165&msg=Lazy+Consensus+Deadline&font=cursive&csz=1>),
we'll proceed with the change.
Thanks all,
Constance
--
Constance Martineau
Senior Product Manager
Email: constance@astronomer.io
Time zone: US Eastern (EST UTC-5 / EDT UTC-4)