Changes to query results in the GitHub Actions API and UI
GitHub has modified the counting mechanism for workflow run queries within the Actions API and UI. The system now prioritizes query accuracy over exact record precision when filtering by workflow, event, status, or branch.
Verified State Diff
Impact & Verification Analysis
Developers and DevOps engineers who rely on the GitHub Actions API for reporting, auditing, or automated workflow management.
It signals a trade-off between absolute data precision and system performance, which may impact automated tools that require exact record counts for billing, compliance, or strict CI/CD pipeline monitoring.
Full Fact Overview
This change indicates a shift in the underlying database query architecture for GitHub Actions, likely moving from a strict count (which can be computationally expensive and prone to timeouts on large datasets) to an estimated or optimized count. By sacrificing exact precision for accuracy, GitHub is likely implementing a more performant indexing strategy or utilizing a different data aggregation layer to handle the high volume of workflow execution metadata. This is a common architectural pattern in distributed systems to ensure UI responsiveness and API stability during high-load scenarios.