Raul824 opened a new issue, #55489: URL: https://github.com/apache/airflow/issues/55489
### Description We migrated control M to airflow around 2023. It was a mass migration and we tried to replicate the logic and use Airflow in whatever we could do best. Our most dags were dependent on each other on date basis instead of time so we used execution_date_fn to achieve the dependency functionality. It was working all good till 2.x versions. But now am facing a peculiar issue with asset aware schedules. We grouped multiple batch jobs into a single dag using taskgroups according to the area of those batch jobs. These taskgroups have external task sensor as well depending on other taskgroup in external dags. This all works fine in cases if a Dag is Scheduled or being triggered by TriggerDagrunOperator. But now due to changes in AssetAwareScheduling in Airflow 3.x the migration which I have to do is stuck as the dags being triggered by AssetAwareScheduling are not having data_interval_start and data_interval_end. How do I set the dependencies now as my external dags are having logical_date value 2025-09-01 13:59:00+00:00 But the asset aware ones have logical_date=None data_interval_start=None data_interval_end=None So if there is a delay and due to which the DAG A with logical date value 2025-09-01 13:59:00+00:00 triggered the DAG B with asset aware scheduling, how do I check whether DAG C for 2025-09-01 13:59:00+00:00 has completed or not. In Airflow 2.x versions I was able to check all external dags using data_interval_start. But now I am lost. Airflow 2.x <img width="1143" height="967" alt="Image" src="https://github.com/user-attachments/assets/67cd7c9c-ddee-4d06-888e-d8297c720865"; /> Airflow 3.x <img width="1027" height="1094" alt="Image" src="https://github.com/user-attachments/assets/d487d5b2-0d5e-4296-b749-15299180a4ae"; /> Any suggestions would be helpful as I have to migrate 728 dags which consist of 1612 task groups. ### Use case/motivation _No response_ ### Related issues _No response_ ### Are you willing to submit a 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]
