You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "hacherix (via GitHub)" <gi...@apache.org> on 2026/06/16 07:16:25 UTC

[I] NOTSET logical_date in TriggerDagRunOperator increment DAG version each run [airflow]

hacherix opened a new issue, #68612:
URL: https://github.com/apache/airflow/issues/68612

   ### Under which category would you file this issue?
   
   Airflow Core
   
   ### Apache Airflow version
   
   3.2.1
   
   ### What happened and how to reproduce it?
   
   DAG versions keep increasing with each run when using `TriggerDagRunOperator`.
   <img width="248" height="131" alt="Image" src="https://github.com/user-attachments/assets/70e97298-99ce-4412-953b-55fe5bfab803" />
   Removing the task resolves the issue.
   And setting `logical_date` to `None` in the operator also resolves the issue.
   When `logical_date` is left to its default value the issue still occurs (seems to default to `timezone.utcnow()`).
   ```python
       TriggerDagRunOperator(
           task_id="trigger_dag",
           trigger_dag_id="trigerred_dag_id",
           logical_date=None,
           wait_for_completion=False,
       )
   ```
   <img width="272" height="136" alt="Image" src="https://github.com/user-attachments/assets/58e9d445-a499-44ea-8eec-3d56398d032d" />
   
   The last 3 runs use a version with `logical_date` set to `None`.
   
   ### What you think should happen instead?
   
   The `logical_date` of `TriggerDagRunOperator` should not be serialized to determine a DAG version. In my opinion this defeats the purpose of DAG versionning when using `TriggerDagRunOperator`.
   
   ### Operating System
   
   _No response_
   
   ### Deployment
   
   Other Docker-based deployment
   
   ### Apache Airflow Provider(s)
   
   _No response_
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Official Helm Chart version
   
   Not Applicable
   
   ### Kubernetes Version
   
   _No response_
   
   ### Helm Chart configuration
   
   _No response_
   
   ### Docker Image customizations
   
   _No response_
   
   ### Anything else?
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] logical_date in TriggerDagRunOperator increment DAG version each run [airflow]

Posted by "Abdulrehman-PIAIC80387 (via GitHub)" <gi...@apache.org>.
Abdulrehman-PIAIC80387 commented on issue #68612:
URL: https://github.com/apache/airflow/issues/68612#issuecomment-4716113698

   Thanks for the report! I couldn't reproduce this on `main` — serializing a DAG with a default-`logical_date` `TriggerDagRunOperator` twice gives an identical DAG-version hash (same for `logical_date=None`), so no version bump.
   
   The default isn't `utcnow()` — it's stored as the `NOTSET` sentinel and only resolved to `utcnow()` at execute time, so it's never serialized.
   
   Could you retest on **3.2.2**/`main` and share a minimal DAG + how you're seeing the version increment? That'll help narrow it down.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] logical_date in TriggerDagRunOperator increment DAG version each run [airflow]

Posted by "justinpakzad (via GitHub)" <gi...@apache.org>.
justinpakzad commented on issue #68612:
URL: https://github.com/apache/airflow/issues/68612#issuecomment-4723708949

   We had the same issue. I think it was fixed in #65222.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] logical_date in TriggerDagRunOperator increment DAG version each run [airflow]

Posted by "venkatamandavilli-code (via GitHub)" <gi...@apache.org>.
venkatamandavilli-code commented on issue #68612:
URL: https://github.com/apache/airflow/issues/68612#issuecomment-4724861087

   Thanks for the detailed report.
   
   This looks like an important issue because DAG versioning should ideally reflect meaningful DAG definition changes, not runtime-generated values that change on every run.
   
   The observation that setting `logical_date=None` stops the version from increasing is useful. It suggests that the default `logical_date` value in `TriggerDagRunOperator` may be introducing a dynamic timestamp into the serialized DAG representation, which then causes Airflow to treat each run as a new DAG version.
   
   From an operational perspective, this could create confusion in environments that rely on DAG version history for auditing, troubleshooting, and deployment traceability. If the DAG structure has not changed, the version should probably remain stable.
   
   It may be worth checking whether `logical_date` should be excluded from the serialized fields used for DAG version comparison, or whether the operator default should avoid evaluating a dynamic timestamp at parse/serialization time.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] logical_date in TriggerDagRunOperator increment DAG version each run [airflow]

Posted by "jroachgolf84 (via GitHub)" <gi...@apache.org>.
jroachgolf84 closed issue #68612: logical_date in TriggerDagRunOperator increment DAG version each run
URL: https://github.com/apache/airflow/issues/68612


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] NOTSET logical_date in TriggerDagRunOperator increment DAG version each run [airflow]

Posted by "boring-cyborg[bot] (via GitHub)" <gi...@apache.org>.
boring-cyborg[bot] commented on issue #68612:
URL: https://github.com/apache/airflow/issues/68612#issuecomment-4715947436

   Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] logical_date in TriggerDagRunOperator increment DAG version each run [airflow]

Posted by "hacherix (via GitHub)" <gi...@apache.org>.
hacherix commented on issue #68612:
URL: https://github.com/apache/airflow/issues/68612#issuecomment-4718110621

   Thanks for the swift answer!
   Following your message I could not replicate it either from a clean install even with the version 3.2.1.
   But looking at our metadata database, I noticed that the dag version ID was increasing with each daily run even though the source code and its hash did not change though. I did not find any other information.
   I guess you can close this issue. Sorry!


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org