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 with out of sync asset counter in the UI. Consider a scenario with a DAG scheduled to run based on three assets. If you delete the queued asset events after one update of asset A, and then subsequently update asset B and C the UI looks like the image below until asset A is updated again (at which point it will run the dag, as intended).

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

• I agree to follow this project's Code of Conduct