GitHub is changing how GitHub Actions reports the size of large workflow-run query results. For searches filtered by workflow, event, status, branch, or actor, any result set exceeding 2,500 records will now be represented as 2,500+ instead of an attempted exact count. GitHub announced the change on September 25, 2026, and said it was rolling out on github.com and GitHub Enterprise Cloud.
Why Exact Counts Are Going Away
According to GitHub, queries covering more than 2,500 workflow runs frequently time out. The count returned in those cases could reflect only the records found before the timeout, rather than the true total. Replacing that incomplete figure with an explicit lower bound is intended to make the result less precise but more accurate while improving query performance.
Pagination Remains Limited
The adjustment affects the reported count, not the existing pagination ceiling. GitHub will continue returning paginated workflow-run results of up to 1,000 items. Developers therefore cannot interpret the 2,500+ indicator as permission to enumerate every matching record through the same broad request; it signals that the query covers an open-ended set beyond the threshold.
Integrations May Need Narrower Filters
Scripts and integrations that depend on retrieving more than 2,500 matching workflow runs from one query will need to divide the request into smaller ranges. GitHub specifically recommends narrowing filters, such as adding date ranges, so each query targets the required runs more precisely.
The practical impact depends on how consumers use the API response. Dashboards that only need to show that a large backlog exists may be able to display the lower-bound count directly. Reporting systems, archival jobs, or audits that require exact coverage must instead partition their searches and manage possible overlap between those narrower result sets.
A Clearer Failure Boundary
The change replaces a potentially misleading exact-looking value with a defined overflow state. It also separates two API concerns: the count communicates that more than 2,500 records match, while pagination still governs how many workflow runs can be returned. Consumers should treat those values as separate limits when updating their handling of large GitHub Actions histories.
AI-generated editorial illustration; not a documentary photograph.
Source: Changes to query results in the GitHub Actions API and UI
SIGNAL TITANS
Leave a Reply