The "Trigger again with this config" behavior can be misleading

[je-enf]

Under which category would you file this issue?

Airflow Core

Apache Airflow version

3.2.1

What happened and how to reproduce it?

Hello,

Consider the following minimal example:

from datetime import datetime, UTC

from airflow.providers.standard.operators.python import PythonOperator
from airflow import DAG
from airflow.sdk import Param, get_current_context
import logging


def parse_params():
    ctx = get_current_context()
    logging.error(ctx["params"])


with DAG(
    dag_id="test_params",
    start_date=datetime(2026, 1, 1, tzinfo=UTC),
    params={
        "my_param": Param(type="string", default="mystring"),
    },
    render_template_as_native_obj=True,
) as dag:
    trigger_batch = PythonOperator(
        task_id="parse_param",
        python_callable=parse_params,
    )

As this DAG contains a Param object, triggering it will always bring up the parameters UI.
If I trigger it a first time with a given parameter for my_param, say 'foo', and then select that run, click "Trigger again with this config" and change 'foo' to 'bar', the value in the params dict of the context still contains 'foo'.

What you think should happen instead?

Either skip the parameters UI in that scenario or update the params with the new given values.

Operating System

debian

Deployment

None

Apache Airflow Provider(s)

No response

Versions of Apache Airflow Providers

No response

Official Helm Chart version

1.21.0 (latest released)

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

[boring-cyborg]

Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.