venkatamandavilli-code commented on issue #68252: URL: https://github.com/apache/airflow/issues/68252#issuecomment-4732346787
Thanks for reporting this and for identifying the behavior around `logical_date`. Based on the reproduction steps, it appears that the DAG definition itself remains unchanged, but a dynamic value associated with `TriggerDagRunOperator` may be influencing the serialized representation used for DAG version calculation. From an operational perspective, DAG versions are most useful when they reflect meaningful changes to the DAG structure or configuration. If a runtime-generated value causes the version to increment on every execution, it becomes more difficult to use version history for deployment tracking, auditing, and troubleshooting. The fact that the behavior disappears when `logical_date=None` is specified seems like an important clue. It may be worth reviewing whether the operator's default logical date handling introduces a value that changes between parses and whether that value should participate in DAG serialization or version comparison. This seems particularly relevant for environments that make extensive use of `TriggerDagRunOperator` and rely on DAG version history to understand when actual workflow definitions have changed. -- 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]
