manipatnam opened a new issue, #60512: URL: https://github.com/apache/airflow/issues/60512
### Apache Airflow version 3.1.6 ### If "Other Airflow 3 version" selected, which one? 3.2.0 ### What happened? When a user who does not have sufficient permissions to backfill a DAG attempts to run a backfill and selects a date range, the UI displays the message: `No runs matching selected criteria.` This message is misleading. The issue is not that there are no matching runs, but that the user lacks the required permissions to perform a backfill. Instead, the UI should clearly indicate that the action failed due to insufficient permissions, which would help users understand and resolve the issue more quickly. <img width="883" height="664" alt="Image" src="https://github.com/user-attachments/assets/3db8500c-8068-4ac2-a57b-57d1a25a43c9"; /> ### What you think should happen instead? If a user without backfill permissions attempts to backfill a DAG, the UI should display an explicit error such as: `Insufficient permissions to backfill this DAG` or a similar authorization-related message <img width="890" height="698" alt="Image" src="https://github.com/user-attachments/assets/99c5b458-3473-43af-b9b0-1c5dffda133a"; /> ### How to reproduce 1. Create or use an existing DAG. 2. Create a user with insufficient permissions (e.g., no backfill or DAG run creation permissions). 3. Log in as this restricted user. 4. Navigate to the DAG in the Airflow UI. 5. Attempt to Backfill the DAG. 6. Select a valid date range. 7. Observe the message shown after submitting the backfill request. ### Operating System debian ### Versions of Apache Airflow Providers _No response_ ### Deployment Astronomer ### Deployment details _No response_ ### Anything else? _No response_ ### Are you willing to submit PR? - [x] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
