nothingmin commented on PR #54119: URL: https://github.com/apache/airflow/pull/54119#issuecomment-3164784926
Thank you for your feedback! To clarify the issue: We have a DAG that is scheduled to run every 10 minutes, and it uses the TriggerDagRunOperator to trigger another DAG. Previously (in Airflow 2), the triggered DAG run’s data_interval would be set based on the logical_date specified at trigger time (so the downstream DAG run would process the correct interval). However, in Airflow 3, the data_interval of the triggered DAG run is instead set based on the time when the run is queued, not the intended logical date. As a result, the downstream DAG receives an unexpected data interval that does not match the desired scheduling semantics. I believe this is a bug rather than an intentional breaking change, since triggering workflows for specific time intervals is a core use case, especially when chaining DAGs for partitioned data processing. This PR is intended to restore the correct behavior for triggered DAG runs. I am attaching screenshots of the same DAG run’s details in both Airflow 2 and Airflow 3 for comparison. <img width="578" height="558" alt="스크린샷 2025-08-08 오전 12 43 00" src="https://github.com/user-attachments/assets/ea00f376-b158-4f1d-b3c8-2d8eefb3c0e8"; /> <img width="554" height="629" alt="스크린샷 2025-08-08 오전 12 44 28" src="https://github.com/user-attachments/assets/a9f3cd74-00d5-458b-b164-9696c22d3bb6"; /> Please let me know if you’d like more detailed examples or further clarification! -- 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]
