Apache Airflow version:
Other Airflow 2 version (please specify below)

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

What happened?
When a DAG is deleted, its entry is not removed from the ab_view_menu table in the Airflow metadata database. As a result, even deleted DAG IDs continue to appear in the Airflow UI when assigning permissions to roles. This causes confusion and can lead to accidental permission assignments to non-existent DAGs.

What you think should happen instead?
When a DAG is deleted, the corresponding entry for that dag_id should also be removed from the ab_view_menu table so that only active DAGs are available for permission assignment in the Airflow UI.

How to reproduce

1. Delete a DAG from your Airflow instance.
2. Check the ab_view_menu table in the metadata database; the old DAG ID remains.
3. Go to the Airflow UI and attempt to assign permissions to a role; deleted DAG IDs are still listed.

Operating System
Please specify your operating system details (e.g., output of cat /etc/os-release).
linux

Versions of Apache Airflow Providers
Please specify provider versions if relevant, e.g. pip freeze | grep apache-airflow-providers.

Deployment
Please select your deployment type (e.g., Docker-Compose, Helm Chart, etc.).
helm deployment

Deployment details
Add any extra details about your deployment (e.g., version of Docker, Kubernetes, etc.).

Anything else?
Issue occurs consistently