### Under which category would you file this issue? Airflow Core ### Apache Airflow version 3.2.2rc1 ### What happened and how to reproduce it? User is able to change the state of the dagrun to the same state it was in. (Success -> Success) OR (Failed -> Failed) 1. Start airflow instance on 3.2.2rc1. 2. Create a dagrun and try to change the state of the dagrun to same state it was in. 3. Earlier this was not possible. (If dagrun was success then success button would be disabled for the user) https://github.com/user-attachments/assets/083cabbc-e6b0-4627-ac05-f77d51b0f36a ### What you think should happen instead? _No response_ ### Operating System Linux ### Deployment None ### Apache Airflow Provider(s) _No response_ ### Versions of Apache Airflow Providers _No response_ ### Official Helm Chart version Not Applicable ### Kubernetes Version _No response_ ### Helm Chart configuration _No response_ ### Docker Image customizations _No response_ ### Anything else? _No response_ ### Are you willing to submit PR? - [ ] 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)
Under which category would you file this issue?
Airflow Core
Apache Airflow version
3.2.2rc1
What happened and how to reproduce it?
User is able to change the state of the dagrun to the same state it was in. (Success -> Success) OR (Failed -> Failed)
Screen.Recording.2026-05-22.at.12.34.24.PM.mov
What you think should happen instead?
No response
Operating System
Linux
Deployment
None
Apache Airflow Provider(s)
No response
Versions of Apache Airflow Providers
No response
Official Helm Chart version
Not Applicable
Kubernetes Version
No response
Helm Chart configuration
No response
Docker Image customizations
No response
Anything else?
No response
Are you willing to submit PR?
Code of Conduct