MartinEmilJakobsen opened a new issue, #53817: URL: https://github.com/apache/airflow/issues/53817
### Apache Airflow version 3.0.3 ### If "Other Airflow 2 version" selected, which one? _No response_ ### What happened? When I delete a queued asset events for a DAG the deletion is not reflected in the UI. More specifically, the webserver UI still shows the asset updates and timestamps that were there prior to the deletion, but the scheduler is working as intended. Therefore you can end up the a DAG scheduled to run on update of three assets. If you delete the queued asset events after one update of asset A, and then update asset B and C the UI looks like the image below until asset A is updated again. <img width="1348" height="65" alt="Image" src="https://github.com/user-attachments/assets/794981a2-11c1-436c-9b43-0ce55836f95d"; /> ### What you think should happen instead? The webserver needs to query the queued events instead of using a cache. ### How to reproduce Create DAG ``` @dag( schedule=[ Dataset("A"), Dataset("B"), ], catchup=False, start_date=pendulum.datetime(2025, 4, 1, tz="Europe/Copenhagen"), dagrun_timeout=datetime.timedelta(minutes=30), ) def test(): sleep(1) ``` * Create Asset A event * Use REST API to delete queued asset events for test-DAG ``` requests.delete( f"{base_url}/api/v2/dags/test/assets/queuedEvents", headers=headers ) ``` * Create Asset B event ### Operating System Ubuntu ### Versions of Apache Airflow Providers _No response_ ### Deployment Official Apache Airflow Helm Chart ### 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]
