Copy button on a Dag run's config copies only one run config

[anteverse]

Apache Airflow version

2.8.0

If "Other Airflow 2 version" selected, which one?

No response

What happened?

Hi, I believe I hit a case where the run config that's exported when we click "Copy" does not seem to be updated when we switch from one run to another in the UI.
The copied json of the run config is always the same.

What you think should happen instead?

I believe the content of the copy should match the right run, and be updated as we switch runs.

Little bit of a clue: being on one run view, if I refresh the page, then I can copy the right json.

How to reproduce

Have this DAG for instance:

with DAG(
    dag_id="issue_copy_button",
    schedule=None,
    catchup=False,
    start_date=pendulum.today("UTC").add(days=-1),
    params={
        "list_of_strings": Param(
            [],
            type="array",
            title="List of strings",
            items={"type": "string"},
        ),
    },
) as dag:

    @task
    def my_task() -> None:
        print("Task done")

    my_task()

Now in the UI:

1. trigger a first run with: ["a", "b", "c"] then a second run with ["d", "e", "f"].
2. open the last run. Press "Copy" on the run config. You get the json of the set of values for this run, hence {"list_of_strings": ["d", "e", "f"]}
3. now open the other run (on the left panel). Press "Copy" on the run config. You will still get the same json as before, hence {"list_of_strings": ["d", "e", "f"]} instead of {"list_of_strings": ["a", "b", "c"]} which matches the currently opened run.

Tested in 2.8.0 and 2.7.3.

Let me know you need more details or if there's anything I should do differently. I could not find a matching existing issue, but feel free to close if there's one.

Thank you!

Operating System

Airflow on Kubernetes

Versions of Apache Airflow Providers

No response

Deployment

Official Apache Airflow Helm Chart

Deployment details

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.

[Taragolis]

I guess it similar to #34846 and might be even fixed by #34904

[Taragolis]

Well nope, it still persists in current main

[anteverse]

Thanks a lot, looking forward to the next releases.