Overview of Query Result Adjustments

GitHub has announced significant adjustments to how workflow run queries behave across its platform. According to the official [GitHub Changelog](https://github.blog/changelog/2026-09-25-changes-to-query-results-in-the-github-actions-api-and-ui/), queries for workflow runs in both the API and user interface now return a less precise but ultimately more accurate count of records when users search by parameters such as workflow, event, status, branch, or actor.

These adjustments affect how large datasets are handled during search operations. Developers and platform administrators frequently run searches to audit, monitor, or manage CI/CD pipelines, making query performance and reliability vital to daily engineering workflows.

Under the previous system, queries attempting to calculate exact numbers for massive result sets frequently encountered performance bottlenecks. The platform aims to resolve these systemic issues through a newly established reporting threshold.

Understanding the New 2,500 Threshold

A key component of this update involves setting a clear ceiling for record count precision. While pagination remains supported for up to 1,000 items, searches yielding massive volumes of data require a different handling strategy.

Specifically, if the number of found records exceeds 2,500, the system will now report a designation of '2,500+' rather than attempting to calculate and return the exact number of matching records.

This operational shift is designed to prevent performance degradation. Queries that previously attempted to retrieve more than 2,500 records frequently experienced timeouts, which historically resulted in returning only the partial number of records found prior to the timeout rather than the true, complete count.

By implementing this strategic limit, GitHub states that overall counts will be significantly more accurate while simultaneously improving execution performance for all customers utilizing the platform.

Impact on Integrations and Automated Scripts

Development teams that rely heavily on automated scripts, custom reporting tools, or third-party integrations should carefully review their codebase. Scripts that expect an exact integer response exceeding 2,500 total matches may need modifications to accommodate the new '2,500+' string or threshold indicator.

For workflows or integrations that strictly require retrieving more than 2,500 matching workflow runs from a single query, GitHub recommends narrowing search filters. For instance, developers can incorporate specific date ranges or additional criteria to isolate and retrieve the exact runs they need without triggering the threshold limit.

Properly scoping API requests ensures that automation tools continue to function smoothly without encountering truncated data or unexpected response formats.

Deployment Schedule and Platform Availability

The changes to query results are rolling out gradually across the ecosystem. Users can expect to see these updates taking effect immediately on github.com as well as for organizations utilizing GitHub Enterprise Cloud.

As cloud infrastructure scales to handle increasing volumes of continuous integration data, platform optimizations such as this remain essential for maintaining responsiveness across both the web interface and programmatic endpoints.

Developers seeking more information on interacting with workflow listings programmatically can review the official documentation for the [GitHub Actions API](https://docs.github.com/rest/actions/workflow-runs#list-workflow-runs-for-a-repository) to understand parameter requirements and response schemas.

Broader Context in Platform Maintenance

This query result modification is part of an ongoing series of updates and refinements to platform features. Engineering teams monitoring platform changes can also review other recent updates, such as the policy regarding how [Expired GitHub Actions artifacts no longer shown in UI and API](https://github.blog/changelog/2026-09-24-expired-github-actions-artifacts-no-longer-shown-in-ui-and-api), which helps declutter storage and streamline data visibility.

Staying informed about these incremental backend adjustments ensures that development teams can maintain robust pipelines, secure supply chains, and efficient automation architectures as the platform continues to evolve.

Administrators are encouraged to consult the [Back to changelog](https://github.blog/changelog/) section on the main blog for a comprehensive archive of weekly updates, deprecation notices, and feature rollouts affecting their development environments.

Sources

• GitHub ChangelogChanges to query results in the GitHub Actions API and UI