jscheffl opened a new issue, #65716:
URL: https://github.com/apache/airflow/issues/65716

   ### Under which category would you file this issue?
   
   Airflow Core
   
   ### Apache Airflow version
   
   3.2.1
   
   ### What happened and how to reproduce it?
   
   After upgrade to Airflow 3.2.1 users report that the "Trigger again with the 
config" is not working as expected.
   
   1. Form with pre-filled config is opening
   2. Change of parameters is possible
   3. If you then trigger, it is used the previous values, it is NOT respecting 
changes
   
   Though if the dict in the advanced section is changed, this is affecting the 
form fields and is used to trigger. But changes in the form are not propagated 
down to the dictionary. See recorded video as example:
   
   
https://github.com/user-attachments/assets/2cfe4330-86c0-4293-afd3-08aeed031c3c
   
   ### What you think should happen instead?
   
   Changes in the form fields should also adjust values to be triggered same 
like if you trigger w/o previous configuration.
   
   ### Operating System
   
   Windows or Linux. Also independnt of browser (Chrome and FF tested)
   
   ### Deployment
   
   Official Apache Airflow Helm Chart
   
   ### Apache Airflow Provider(s)
   
   _No response_
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Official Helm Chart version
   
   1.19.0
   
   ### 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)
   


-- 
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]

Reply via email to