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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
