Repository navigation
Description
Apache Airflow version
Other Airflow 3 version (please specify below)
If "Other Airflow 3 version" selected, which one?
3.1.6
What happened?
When deactivating a DAG by removing it from the DAGS_FOLDER, you can still access it on the UI by visiting its old URL.
However there is no indication that the DAG was deactivated. Additionally, if it was active before deletion:
- its state is still active
- a
Next Rundatetime is displayed
What you think should happen instead?
The UI should indicate that the DAG has been deactivated.
How to reproduce
- remove a an active DAG from
DAGS_FOLDER - await DAG processing
- open the now deactivated DAG's UI via its URL
Operating System
Linux via the standard docker-compose file
Versions of Apache Airflow Providers
apache-airflow-providers-amazon==9.19.0
apache-airflow-providers-celery==3.15.0
apache-airflow-providers-cncf-kubernetes==10.12.0
apache-airflow-providers-common-compat==1.11.0
apache-airflow-providers-common-io==1.7.0
apache-airflow-providers-common-messaging==2.0.1
apache-airflow-providers-common-sql==1.30.2
apache-airflow-providers-docker==4.5.1
apache-airflow-providers-elasticsearch==6.4.2
apache-airflow-providers-fab==3.1.1
apache-airflow-providers-ftp==3.14.0
apache-airflow-providers-git==0.2.0
apache-airflow-providers-google==19.3.0
apache-airflow-providers-grpc==3.9.1
apache-airflow-providers-hashicorp==4.4.1
apache-airflow-providers-http==5.6.2
apache-airflow-providers-microsoft-azure==12.10.1
apache-airflow-providers-mysql==6.4.0
apache-airflow-providers-odbc==4.11.0
apache-airflow-providers-openlineage==2.9.2
apache-airflow-providers-postgres==6.5.1
apache-airflow-providers-redis==4.4.1
apache-airflow-providers-sendgrid==4.2.0
apache-airflow-providers-sftp==5.5.1
apache-airflow-providers-slack==9.6.1
apache-airflow-providers-smtp==2.4.1
apache-airflow-providers-snowflake==6.8.1
apache-airflow-providers-ssh==4.2.1
apache-airflow-providers-standard==1.10.2
Deployment
Official Apache Airflow Helm Chart
Deployment details
Docker-Compose
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
Activity
boring-cyborg commentedon Mar 17, 2026
Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.
jroachgolf84 commentedon Mar 17, 2026
@yavin87 - just curious, what happens if you try to run the DAG?
bbovenzi commentedon Mar 18, 2026
Sounds like this is a deeper issue since the API is also returning information about the dag.
TomasCorreia2003 commentedon Mar 27, 2026
I have an implemented fix for this bug
Fix apache#63800: Show deactivated status for stale DAGs in the UI
Fix apache#63800: Show deactivated status for stale DAGs in the UI
Show deactivated DAG state in UI (apache#63800)
Show deactivated DAG state in UI (apache#63800)
Fix DAG header test typing after rebase (apache#63800)
Fix stale DAG details actions in the UI (apache#63800)
Rerun WebKit UI e2e workflow for stale DAG UI PR (apache#63800)
Fix stale DAG UI review follow-ups (apache#63800)
Show deactivated DAG state in UI (apache#63800)
Fix DAG header test typing after rebase (apache#63800)
Fix stale DAG details actions in the UI (apache#63800)
Fix stale DAG UI review follow-ups (apache#63800)
UI: Show deactivated state for stale DAGs
[v3-2-test] UI: Show deactivated state for stale DAGs (#65214)
UI: Show deactivated state for stale DAGs (apache#65214)
[v3-2-test] UI: Show deactivated state for stale DAGs (#65214) (#65218)
[v3-2-test] UI: Show deactivated state for stale DAGs (#65214) (#65218)
[v3-2-test] UI: Show deactivated state for stale DAGs (#65214) (#65218)
[v3-2-test] UI: Show deactivated state for stale DAGs (#65214) (#65218)
[v3-2-test] UI: Show deactivated state for stale DAGs (#65214) (#65218)