Ui Dags List endpoint should sort by last_run_after instead last_run_start_date #56073
Description
Apache Airflow version
main (development)
If "Other Airflow 2 version" selected, which one?
No response
What happened?
Unexpected behavior of how dags are sorted when you trigger a dag run from the dags list.
What you think should happen instead?
Queued runs don't have a start date. We should sort by run_after instead.
How to reproduce
On the dags list, sort the list by last_run_start_date, then trigger a dag run from the list from a dag for any dag except the first one.
Watch the list jump around as the run goes from queued to running. Or watch nothing happen if the dag is briefly pushed off the first page.
Operating System
all
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