Inconsistent Queued Dag Count Between Dashboard and Dag List Page

[choo121600]

Apache Airflow version

main (development)

If "Other Airflow 2 version" selected, which one?

No response

What happened?

On the Airflow Dashboard, the "Queued Dags" count (e.g., 1) is displayed correctly.
However, clicking on this stat redirects to the Dag list page with the filter ?last_dag_run_state=queued, and the page shows "No Dag found", even though queued Dags exist.

Screen.Recording.2025-07-02.at.1.22.37.AM.mov

What you think should happen instead?

The Dag list page should correctly display the Dags that have queued Dag runs, consistent with the number shown on the Dashboard.

How to reproduce

1. Go to the Airflow Dashboard
2. Note the number shown under "Queued Dags" (e.g., 1)
3. Dag list page opens with the URL filter: ?last_dag_run_state=queued
4. Page shows "No Dag found", despite the Dashboard indicating there are queued Dags

Operating System

mac os

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

[tirkarthi]

The dashboard doesn't auto refresh. So is there a possibility that while dashboard was loaded there was a queued dagrun and after a few moments it got to running state while dashboard was not updated but dags list made a fresh query where there was no queued state dagrun.

[choo121600]

@tirkarthi I verified that in my environment, the Dag remains in the 'queued' state even after refreshing the dashboard. However, the Dag does not appear on the Dag list page, and this issue persists despite refreshing that page as well.

Upon investigation, it seems that the root cause of this inconsistency is a difference in the filter criteria used internally by the two pages.

It appears that this issue occurs with DAGs that have been triggered and are in the 'queued' state, but do not have a start_date yet — in other words, runs that are pending execution but not yet actively started.

Screen.Recording.2025-07-02.at.2.11.19.AM.mov