Unable to show both enabled and disabled dags at the same time (the `All` option is unresponsive when `hide_paused_dags_by_default` is set to `True`)

[zachliu]

Apache Airflow version

3.0.3

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

Airflow 2.x versions do not have this issue

What happened?

When hide_paused_dags_by_default is set to True, the All option in the drop-down menu on the UI is unresponsive.

When the Disabled was checked, clicking on All just went back to Enabled ¯\_(ツ)_/¯

bug-report.mp4

What you think should happen instead?

In Airflow 2.x the behavior is correct when hide_paused_dags_by_default is set to True:

• the default view is Active dags
• the All tab still shows all dags both enabled and disabled.

How to reproduce

1. set hide_paused_dags_by_default to True
2. go to the UI and try to select the All option from the drop-down.

Operating System

LM 21.3 with docker python:3.12-slim-bookworm

Versions of Apache Airflow Providers

No response

Deployment

Docker-Compose

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]

I am unable to reproduce this in main and 3.0.3 . When you select the filter do you see "reset filter" button at the right above sorting? Does clicking on "reset filter" reset it to all and display all dags? Do you see any API calls issue in network tab while changing to all?

[zachliu]

@tirkarthi there is no reset filter button anywhere on the UI 😕

[zachliu]

Do you see any API calls issue in network tab while changing to all?

as i said, the button is unresponsive. there was no api calls registered in the logs when i switched to all

[yokwejuste]

I am unable to reproduce this in main and 3.0.3 . When you select the filter do you see "reset filter" button at the right above sorting? Does clicking on "reset filter" reset it to all and display all dags? Do you see any API calls issue in network tab while changing to all?

The reset is supposed to be the "All" on the UI showing both Enabled and Disabled dags.

[yokwejuste]

@zachliu, Not sure this relevant, since all working well on my end (as expected)!!!

result.mp4

• You would not see any particular API since for some reasons

Frontend API calls are cached using react-query, which allows for efficient data fetching and avoids unnecessary repeat requests within the same browser session or component lifecycle.

• At the start we have two particular endpoints hit for the All functionality which is cached.

---

Each Frist Time you use the Enabled or Disabled functionality, you get the API. Check the screenshot below after clearing off.

---

---

Finally, Cached data is reused for subsequent queries with the same key, avoiding unnecessary network calls.

[zachliu]

@yokwejuste yes i knew they reused cached data. and i checked the api calls and everything before creating this issue. the api calls are the same as shown in your screenshots. but for me the All option in this drop-down can never be checked. i see in your screen record you could check All (literally, the check mark on its right), which i could never do for some reason

clicking All does nothing

[yokwejuste]

Hey @zachliu, It is normal.
It was sent already when the page loaded the first time.

To confirm what I say:

• Hit this: http://127.0.0.1:8000/dags?paused=false
• Click on the All option again and you will see a hit

This is because this time around the first load triggered instead the Enabled

[zachliu]

@yokwejuste 😂 wish we could do a live call and screen share

• http://127.0.0.1:8000/dags?paused=false leads me to the page where Enabled being checked
• clicking on the All option still does nothing and the url just jumped back to http://127.0.0.1:8000/dags without a page load

Screencast.2025-07-21.11.10.49.mp4

[yokwejuste]

This is what I am taking about here. Try having a look at this one and tell me if it is clearer now. unless you are talking about something else @zachliu 😆

result.mp4