Triggering a DAG Run from the DAG Graph View does not redirect to the triggered DAG Run page

[pedro-cf]

Apache Airflow version

2.9.1

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

No response

What happened?

Triggering a DAG Run from the DAG Graph View does not redirect to the triggered DAG Run page.

What you think should happen instead?

After Triggering a DAG Run from the DAG Graph View the user should be redirected to the graph view of the DAG RUN he just triggered.

How to reproduce

1. Ensure 'AIRFLOW__WEBSERVER__DAG_DEFAULT_VIEW' is set to 'graph'
2. Click on a DAG that has Parameters.
3. Go to the graph View
4. Click the Trigger DAG Run button.
5. Trigger DAG Run
6. You will not be redirected to the graph view of this latest DAG Run you just triggered.

(see gif above)

Operating System

Debian GNU/Linux 11 (bullseye)

Versions of Apache Airflow Providers

No response

Deployment

Docker-Compose

Deployment details

Docker Compose version v2.2.3

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

[jscheffl]

I do not fully understand what you mean with "the triggered DAG Run page" - do you assume the resulting page after triggering should jump to the details of the "new run just triggered" or what detail do you expect? Also the video recording does not explicitly tell me.
Is this only happening if you configure the graph view as default as you explicitly state this in the details?

Note that when you open the "trigger DAG" view the URL in the browser should contain the "origin-URL" which is used to direct the user back to. Can you please post the origin URL in this case and the URL you expect to be directing to?

[pedro-cf]

do you assume the resulting page after triggering should jump to the details of the "new run just triggered"

Yes, this was working like this up to version 2.8.0 or 2.8.1

Also the video recording does not explicitly tell me

As you can see in the GIF:

1st state: before triggering the DAG Run the current and latest DAG run that is viewed is 2024-03-06, 11:25:14 UTC

2nd state: after triggering the DAG Run, the same previous DAG run is still viewed 2024-03-06, 11:25:14 UTC

3rd state: after click the "GRAPH" button to refresh the page the DAG run displayed is 2024-03-06, 11:18:16 UTC

Is this only happening if you configure the graph view as default as you explicitly state this in the details?

I am unsure of this, but I thought it could be related and would be good to mention.

[jscheffl]

Okay, now I understand and made a small test myself.

The problem described appears actually in tabs "Graph" and "Gantt". Root cause is that the trigger-button renders the parameter &dag_run_id=manual__2024-03-07T21%3A11%3A16%2B01%3A00 into the origin URL, if the trigger page returns to this origin and uses the dag_id in the return call, the page will not have auto-refresh on and therefore will not display the new DAG run.

[jscheffl]

I tested this to fix it finally in Airflow 2.9.0 as upcoming release. I needed to realize that due to changes in UI structure and rework of the layout the problem has been resolved on it's own. As there will be very probably no fix be supplied in Airflow 2.8.x I am going to close this buf. It is implicitly frixed with 2.9.0