gang-zh opened a new issue, #74291: URL: https://github.com/apache/airflow/issues/74291
### Description Allow the Grid view to show more than 50 Dag runs. Today the "Number of Dag Runs" selector in `layouts/Details/PanelButtons.tsx` is hardcoded to `1 / 5 / 10 / 25 / 50` (and narrower screens get even fewer options in Gantt mode). Airflow 2 offered `25 / 50 / 100 / 365` in one click. Proposed options, in order of preference: 1. Add `100` and `365` back to the selector, matching Airflow 2. 2. Or make the selector a free-form number input with a sane upper bound (the API already paginates `dagRuns`, so the backend side is not the constraint). 3. Or expose the option list via a `[webserver]`/`[api]` config so operators can raise the cap for their users. ### Use case/motivation Daily Dags accumulate 365 runs a year; hourly Dags hit 50 runs in two days. With a 50-run ceiling it is no longer possible to eyeball a year of a daily Dag or a week of an hourly Dag in the grid, which was a common debugging workflow on Airflow 2 (spot the first failed day, see how far back a pattern goes). Grid pagination (#65388) helps with reaching old runs but does not replace seeing them side by side. This was raised in the comments of #56250 (Jan 2026) but that umbrella issue was closed with a request to file individual issues, so filing it here. ### Related issues - #56250 (umbrella, closed) - the 50 cap was raised in its comments - #65388 - grid pagination, 3.3.0 - #74281 - the selected limit is currently lost on tab switch; independent of this request but the two together make the grid hard to use for Dags with many runs ### Are you willing to submit a PR? - [x] 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]
