Trigger DAG form submits stale config when reusing a previous run's parameters

[seruman]

Under which category would you file this issue?

Airflow Core

Apache Airflow version

3.2.0

What happened and how to reproduce it?

When retriggering a DAG using Trigger again with this config from a previous run, any edits made to parameters via the Run Parameters form fields are silently discarded on submit. The original prefilled config is sent instead.
Editing the JSON directly in Advanced Options works fine, only the form field edits are lost.

1. Trigger a DAG that has params.
2. After the run completes, click the run and choose Trigger again with this config.
3. The form opens with the previous run's param values prefilled.
4. Edit one of the param values in the form input.
5. Click Trigger.
6. Observe the new DAG run's config, it contains the original prefilled value, not the edit

What you think should happen instead?

Editing params via the form fields should work the same way regardless of whether the dialog was opened fresh or with a prefilled config. The submitted config should always reflect what the user last edited in the form, like in Airflow 2.

Operating System

No response

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

• I agree to follow this project's Code of Conduct