GitHub Actions API and UI Update Limits Precision of Workflow Run Result Counts
GitHub has updated its Actions API and UI to return less precise but more accurate counts of records when filtering workflow runs by parameters like event, status, and branch.
GitHub has announced changes to the way query results for workflow runs are calculated and displayed in both the GitHub Actions API and the user interface. When users search or filter workflow runs by specific dimensions such as workflow name, triggering event, execution status, or target branch, the system will now return an estimated or less precise count of total records to improve query performance.
Primary source
Open GitHub Changelog ↗This article summarizes the source. Check the original for full details and conditions.
Comparison
| Aspect | Before / Alternative | After / This |
|---|---|---|
| Count Precision | Exact integer count of matching workflow runs even across large historical datasets | Less precise or estimated count of matching runs to optimize query response times |
| API Response Fields | Total count fields guaranteed to reflect absolute exact matches | Total count fields may represent rounded or estimated values for deep queries |
| UI Pagination Behavior | Pagination pages calculated using exact, rigid database counters | More fluid pagination relying on high-performance search indices and estimates |
Action Checklist
- Audit internal automation scripts that rely on exact run counts from the GitHub Actions API Update scripts that enforce strict assertion checks on total_count values
- Verify UI integration tools and dashboards relying on precise pagination counts Ensure your parsing logic gracefully handles estimated totals without crashing
- Monitor critical deployment gates using Actions status queries Verify that your deployment gates rely on status checks rather than aggregate count queries
