collinmcnulty opened a new issue, #59337: URL: https://github.com/apache/airflow/issues/59337
### Apache Airflow version 2.11.0 ### If "Other Airflow 2/3 version" selected, which one? _No response_ ### What happened? A dynamically generated dag that uses Asset scheduling sometimes has a brief issue where it is not parsing correctly and Airflow marks it as stale. During the time that it is stale, one of the Assets that it needs to schedule is updated. When it starts parsing correctly again, it does not run, and instead waits until that Asset is updated again. However, this updated Asset does show in the "Dataset updates that triggered your dag run" section of the UI. ### What you think should happen instead? Instead, the Asset updates should still be counted against the stale dag such that when it is no longer stale, it can know that it can run immediately. ### How to reproduce - create a dag that uses asset scheduling - introduce a crash bug so that the dag goes stale - update an asset that the dag uses to schedule - remove the crash bug - observe that the dag does not start ### Operating System debian bullseye ### Versions of Apache Airflow Providers _No response_ ### Deployment Astronomer ### Deployment details _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]
