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

   ### Apache Airflow version
   
   2.9.1
   
   ### If "Other Airflow 2 version" selected, which one?
   
   _No response_
   
   ### What happened?
   
   In the DAG run view, the URL's of the run_id column don't work. 
   
   For example, I have a DAG that ran multiple times. The link in the `dag_id` 
column works as expected:
   
http://localhost:8080/dags/test-task/graph?execution_date=2024-05-14+11%3A39%3A20.673554%2B00%3A00
   (It  adds `&dag_run_id=run_1` to the URL, but that is indeed correct.)
   
   For the same DAG run the link in the `run_id` column is this: 
http://localhost:8080/dags/test-task/graph?dag_run_id=run_1
   
   When clicking this it shows me the latest run of the DAG, and the URL is 
also changed to 
http://localhost:8080/dags/test-task/grid?dag_run_id=run_29&tab=graph
   
   ### What you think should happen instead?
   
   The link in the `run_id` column should take the user to the correct DAG run, 
because RunId's are unique identifiers of runs.
   
   I'm not entirely sure what the link in the `dag_id` column should be. I'm 
fine with that staying as it is now, although I'm not sure what the value is of 
having the same link twice.
   
   ### How to reproduce
   
   - Go to a DAG that ran more than once
   - For a DAG run that wasn't the latest for that DAG, click on the link in 
the `run_id` column. This will still take you to the latest run.
   
   Previously there have been issues with selecting the correct DAG run if they 
were not in the last 25 runs. When doing a fix this should be verified to work. 
   This file creates two DAGs, one to trigger the other one 29 times. (Should 
be larger than your `default_dag_run_display_number`, which is by default 25.)
   
   ```python
   from airflow import DAG
   from airflow.api.common.trigger_dag import trigger_dag
   from airflow.operators.python import PythonOperator
   
   def trigger_dags():
       for i in range(1, 30):
           trigger_dag(
               dag_id='test-task',
               run_id=f'run_{i}',
               conf={ 'run': i},
               replace_microseconds=False
           )
   
   
   with DAG(dag_id="test-trigger", schedule=None) as dag:
       task = PythonOperator(
           task_id='trigger-dags',
           python_callable=trigger_dags
       )
   
   with DAG(dag_id='test-task', schedule=None) as dag2:
       dummy_task = PythonOperator(
           task_id='dummy-task',
           python_callable=lambda params: print(f'this is run nr 
{params.get("run")}')
       )
   ```
   
   ### Operating System
   
   Debian bookwork
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Deployment
   
   Official Apache Airflow Helm Chart
   
   ### Deployment details
   
   Using the official helm chart. I see the problem both on my local k8s 
cluster (on my mac) and in our EKS cluster. 
   
   ### Anything else?
   
   I've tested it with two different browsers (Brave and Safari), same results. 
   
   ### 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