Add support for filtering Dags by any DagRun state

[guan404ming]

Related Issue

• close Backwards backfill UI incorrectly shows “no running tasks” while older backfill task instances are still running #64827

Why

During a backwards backfill the home dashboard reported no running Dags because the running/queued counts only looked at each Dag's latest run, missing an older run still active.

How

• Add support for filtering Dags by any DagRun state
• Make the filter to be dropdown select to prevent the ui being too compact

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)
  Claude Code with Opus4.8

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

[pierrejeambrun]

Thanks, just one question

[Vamsi-klu]

Changing these counts to “any DagRun is running/queued” makes the dashboard card count diverge from the card link. The cards still link to dags?last_dag_run_state=running / queued, and /ui/dags applies that filter to the latest DagRun.

In the backfill case this PR fixes, the Running card can show 1, but clicking it can land on a Dags list that excludes that DAG because its latest run is queued or success.

Could we either add/use a Dags-list filter with matching “any active DagRun state” semantics for these card links, or keep the stats latest-run based so the count and click-through stay aligned?

[guan404ming]

Makes sense. thanks for catching this, you're right that the count and the card link diverged.

I went with the first option: I added a dedicated dag_run_state filter on the /ui/dags endpoint with "any active DagRun" semantics, separate from last_dag_run_state (which still matches the latest run only). The Running/Queued dashboard cards now link to dags?dag_run_state=running / queued, so the count and the click-through stay aligned in the backfill case. The Dags-list state toggle also routes Running/Queued through this any-run filter (Failed/Success keep latest-run semantics) and reflects whichever param is active, so landing from a card highlights the right button.

Just pushed the change and feel free to provide any suggestion about the changes.

[pierrejeambrun]

Nice thanks a few suggestions

[guan404ming]

Thanks for the review. Here are some update:

• Split the single run-state control into two distinct dropdowns: Last run (latest run, all states) and
  Any run (any run). They're independent now, so combinations like latest = success + has a running run
  work, and you can still filter latest = running/queued.
• Limited the Any run filter to running/queued on both ends — the backend _AnyDagRunStateFilter now rejects other states with a 400 (only these have the partial index on dag_run; others would full-scan), and the UI only offers those two.

Screenshot:

Screen.Recording.2026-06-27.at.2.37.02.PM.mov

[pierrejeambrun]

LGTM, a couple of small suggestion. Then we can merge.

[guan404ming]

I think the comments have been resolved and it looks good to merge. Please feel free to let me know or open pr/issue to refine this one, thanks!