You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
17,187 (core quota consumed β includes reads, writes, and all GitHub API operations)
π Safe-Output Writes
70 (28 issues + 17 PRs + 12 comments + 13 discussions created by safe-output tools)
β± Avg Duration
578s (p95: 1,715s)
π GitHub API Calls Trend (90 days)
This is the first data point in the history, so no trend comparison is available yet. Today's total of 17,187 REST API calls (core quota) establishes our baseline. The Workflow Health Manager - Meta-Orchestrator alone consumed 5,916 calls β 34% of today's total β making it the clear API leader from day one. As history accumulates over coming days, trending patterns will become visible.
π GitHub API Calls by Workflow Trend (30 days)
With only a single day of data available, this chart shows today's top workflows as a bar chart. The Workflow Health Manager stands out significantly, consuming nearly 4Γ more API quota than the second-place Copilot Session Insights (1,494 calls). Daily and weekly analysis workflows collectively account for the bulk of API consumption, reflecting their frequent read-heavy operations against GitHub's REST API.
π GitHub REST API Calls Heatmap (90 days)
Insufficient history exists for a calendar heatmap (requires β₯14 data points); the chart shows today's top workflow API consumers as a fallback. Monday 2026-05-04 recorded 17,187 core quota calls across 61 workflow runs β a solid first baseline. Weekly patterns (e.g., weekday spikes vs. weekend quiet) and any recurring heavy-hitter days will become visible as this report accumulates data over the coming weeks.
The Workflow Health Manager - Meta-Orchestrator dominates with 34.4% of all REST API calls (5,916), suggesting significant concentration risk if this workflow's API patterns change. The top 3 workflows (Workflow Health Manager, Copilot Session Insights, Daily Rendering Scripts Verifier) together account for 50% of today's total consumption. The remaining 47 workflows share the other 50%, indicating a healthy long-tail distribution.
π GitHub REST API Consumption by Workflow (last 24h)
The Workflow Health Manager - Meta-Orchestrator leads with 5,916 calls β far below the 15,000/hr hourly limit but worth monitoring if it runs more frequently. All workflows remain comfortably under the hourly cap individually. The Copilot Session Insights workflow's high duration (2,287s avg) combined with 1,494 API calls suggests opportunities to batch or cache GitHub API calls within long-running agent sessions. Consider reviewing the Meta-Orchestrator's API call patterns for potential caching optimizations given its leading position.
Top 10 Workflows by REST API Consumption (last 24h)
Workflow
REST API Calls
Runs
Avg Duration
Workflow Health Manager - Meta-Orchestrator
5,916
1
602s
Copilot Session Insights
1,494
1
2287s
Daily Rendering Scripts Verifier
1,136
1
595s
[aw] Failure Investigator (6h)
989
1
688s
Daily CLI Tools Exploratory Tester
842
1
518s
Weekly Workflow Analysis
834
1
605s
Daily OTel Instrumentation Advisor
829
1
559s
Daily Semgrep Scan
462
1
293s
Weekly Safe Outputs Specification Review
444
1
481s
Copilot Agent Prompt Clustering Analysis
433
1
1757s
Trending Indicators
7-day API trend: β N/A (first data point β no prior history)
30-day API trend: β N/A (first data point β no prior history)
GitHub REST API call rate: 17,187 calls/day over last 1 day (hourly limit: 15,000; all workflows are well within limit)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
π GitHub API Consumption Report
Report Date: 2026-05-04 Β· Repository: github/gh-aw Β· Run: #25316068273
Today at a Glance
π GitHub API Calls Trend (90 days)
This is the first data point in the history, so no trend comparison is available yet. Today's total of 17,187 REST API calls (core quota) establishes our baseline. The Workflow Health Manager - Meta-Orchestrator alone consumed 5,916 calls β 34% of today's total β making it the clear API leader from day one. As history accumulates over coming days, trending patterns will become visible.
π GitHub API Calls by Workflow Trend (30 days)
With only a single day of data available, this chart shows today's top workflows as a bar chart. The Workflow Health Manager stands out significantly, consuming nearly 4Γ more API quota than the second-place Copilot Session Insights (1,494 calls). Daily and weekly analysis workflows collectively account for the bulk of API consumption, reflecting their frequent read-heavy operations against GitHub's REST API.
π GitHub REST API Calls Heatmap (90 days)
Insufficient history exists for a calendar heatmap (requires β₯14 data points); the chart shows today's top workflow API consumers as a fallback. Monday 2026-05-04 recorded 17,187 core quota calls across 61 workflow runs β a solid first baseline. Weekly patterns (e.g., weekday spikes vs. weekend quiet) and any recurring heavy-hitter days will become visible as this report accumulates data over the coming weeks.
π© Top API Burners (24h)
The Workflow Health Manager - Meta-Orchestrator dominates with 34.4% of all REST API calls (5,916), suggesting significant concentration risk if this workflow's API patterns change. The top 3 workflows (Workflow Health Manager, Copilot Session Insights, Daily Rendering Scripts Verifier) together account for 50% of today's total consumption. The remaining 47 workflows share the other 50%, indicating a healthy long-tail distribution.
π GitHub REST API Consumption by Workflow (last 24h)
The Workflow Health Manager - Meta-Orchestrator leads with 5,916 calls β far below the 15,000/hr hourly limit but worth monitoring if it runs more frequently. All workflows remain comfortably under the hourly cap individually. The Copilot Session Insights workflow's high duration (2,287s avg) combined with 1,494 API calls suggests opportunities to batch or cache GitHub API calls within long-running agent sessions. Consider reviewing the Meta-Orchestrator's API call patterns for potential caching optimizations given its leading position.
Top 10 Workflows by REST API Consumption (last 24h)
Trending Indicators
π¦ Cache Memory Status
/tmp/gh-aw/cache-memory/trending/api-consumption/history.jsonlAutomatically generated by the api-consumption-report workflow.
Beta Was this translation helpful? Give feedback.
All reactions