hterik opened a new issue, #34723:
URL: https://github.com/apache/airflow/issues/34723
### Apache Airflow version
2.7.1
### What happened
1. Browse to `AIRFLOW/dagrun/list/?_flt_3_dag_id=my_dag`
2. Click any link from the **Run Id** column, below the most recent 25 runs.
It should take you to
`AIRFLOW/dags/mydag/graph?run_id=scheduled__2023-09-21T00%3A00%3A00%2B00%3A00&execution_date=2023-09-21+00%3A00%3A00%2B00%3A00`
and it does so correctly
3. The graph view opens but **no run is selected.**
When clicking on any item in the graph, the LATEST run is selected in
the grid. If the user is not careful to observe this, they are mislead to
thinking the results they are browsing in the graph is the ones they selected
in step 2.
As workaround, one can append `&num_runs=365` to the url, this will take you
to the correct run from step 2. But eventually you will exhaust 365 runs as
well.
This problem isn't only applicable to the dagrun list. Any links to the
/dags/ graph are affected. We have external systems linking to individual
dagruns that now get unusable after 25 runs.
### What you think should happen instead
When navigating to a run via link, it should **always** present the run that
was provided in run_id querystring.
### How to reproduce
See above
### Operating System
Debian GNU/Linux 11 (bullseye)
### Versions of Apache Airflow Providers
_No response_
### Deployment
Other Docker-based deployment
### Deployment details
_No response_
### Anything else
This was not a problem in Airflow 2.5, regression in 2.7, probably
introduced by new embedded graph view (which otherwise is great :))
### 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]