cb149 opened a new issue #19082: URL: https://github.com/apache/airflow/issues/19082
### Apache Airflow version 2.2.0 (latest released) ### Operating System Debian buster ### Versions of Apache Airflow Providers _No response_ ### Deployment Other Docker-based deployment ### Deployment details Official docker image (extended) ### What happened I have a dag which is scheduled to run every 2 hours. As the last task, it has a TriggerDagRunOperator, which triggers a dag that has `schedule=None`. I've been running this set up for months now, and when I click on `Task Duration`, `Task Tries` or `Landing Times` of the dag without a schedule, all existing information is loaded, which takes a long time and results in an unreadable graph, as it does not limit it to the last 25 runs (Changing runs and clicking "Update" has no effect) and instead shows the data from the first run until the latest run. When I click on one of the UIs, I can also see a spike in CPU usage for my server and `Landing times` actually results in a Timeout and a huge spike in CPU usage. ### What you expected to happen Dags with `schedule=None` should still only show the recent 25 (or whatever number is selected) runs for `Task Duration`, `Task Tries` or `Landing Times`. For Tree view, it works without issues. ### How to reproduce Create a dag with `schedule=None`, trigger it with TriggerDagRunOperator from another dag multiple times and then use the `Task Duration`, `Task Tries` or `Landing Times` UI. ### Anything else _No response_ ### 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]
