karenbraganz opened a new issue, #55515: URL: https://github.com/apache/airflow/issues/55515
### Apache Airflow version 3.0.6 ### If "Other Airflow 2 version" selected, which one? _No response_ ### What happened? Dags that are scheduled based on multiple assets might show an incorrect number of assets updated after a manual run is triggered. I was able to reproduce this on a consumer_dag dependent on 2 assets. Before triggering a manual run, the UI shows "1 of 2 assets updated". <img width="417" height="234" alt="Image" src="https://github.com/user-attachments/assets/a99674c0-23ae-4625-80b4-472c693b806c"; /> When a manual run is triggered, the UI incorrectly displays "0 of 2 assets updated". <img width="428" height="241" alt="Image" src="https://github.com/user-attachments/assets/3e2de242-e891-4ff5-b374-c89928a74fe1"; /> This is incorrect because one of the assets has already been updated. As soon as the other asset is updated, a run will be triggered. Manual runs do not actually reset or delete existing asset events. ### What you think should happen instead? The "assets updated" number displayed on the UI should not change due to a manual run. ### How to reproduce 1. Create a consumer dag that is dependent on 2 assets that are updated by tasks in 2 separate producer dags. 2. Manually trigger the producer_dag1 and notice that the UI will display 1 of 2 assets updated. 3. Manually trigger the consumer_dag and notice that the UI will display 0 of 2 assets updated. This is incorrect. If you trigger producer_dag2 now, the dag will run because the event from producer_dag1 still counts. I have attached example of consumer_dag, producer_dag1, and producer_dag2. [consumer_dag.py](https://github.com/user-attachments/files/22279159/consumer_dag.py) [producer_dag1.py](https://github.com/user-attachments/files/22279158/producer_dag1.py) [producer_dag2.py](https://github.com/user-attachments/files/22279157/producer_dag2.py) ### Operating System Debian GNU/Linux ### 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]
