Changes to query results in the GitHub Actions API and UI
GitHub Actions updated its API and UI query results to cap large workflow run counts at 2,500 plus, preventing timeouts caused by exact counting on massive datasets. The change aims to improve query performance and accuracy, requiring integrations that retrieve larger record sets to use narrower filters.
GitHub updated how the Actions API and interface report workflow run totals. Counts now display a rounded figure when searches match over 2,500 results. The system reports this as “2,500+” rather than calculating an exact number. This change affects queries filtered by workflow, event, status, branch, or actor. Paginated data still submits up to 1,000 items per page. Large searches often timed out before providing accurate totals. The system previously returned partial counts based on time limits rather than true figures. Capping the display improves overall query speed and reliability for users. Administrators relying on bulk data must now apply stricter filters. Adding specific date ranges helps narrow down the required records effectively. This adjustment supports better performance across the platform. The statement does not clarify how many specific timeouts occurred prior to this update. It does not detail the technical steps used to implement the new counting logic. The text does not explain if this limit affects non-workflow related queries. It does not specify when the rollout will be fully complete for all users.