[api-consumption] 📊 GitHub API Consumption Report — 2026-07-16

[github-actions[bot]]

📊 GitHub API Consumption Report

Report Date: 2026-07-16 · Repository: github/gh-aw · Run: #29493910926

⚠️ Partial dataset: the logs collection tool timed out mid-download. 102 runs with complete summaries were captured (all dated 2026-07-16); ~170 run directories did not finish downloading. Today is also a mid-day, in-progress UTC day, so absolute daily totals are understated versus a full day.

---

Today at a Glance

Metric	Value
🤖 Total Runs	102 (71 ✅ / 31 ❌)
🎯 Success Rate	69.6%
🔗 GitHub REST API Calls	86,376 (core quota consumed — includes reads, writes, and all GitHub API operations)
📝 Safe-Output Writes	0 (issues + PRs + comments + discussions actuated by safe-output tools)
⏱ Avg Duration	643.7s (p95: 1334.0s)

---

🔗 GitHub API Calls Trend (90 days)

REST API consumption stays choppy on a ~40K–100K/day baseline punctuated by sharp spikes — a standout 574K on 2026-06-17 and a 276K surge yesterday (2026-07-15). Today's partial total of 86.4K already sits near the 7-day rolling average (~100K/day), so the day is trending in line with recent volume despite the incomplete capture.

---

🔗 GitHub API Calls by Workflow Trend (30 days)

The Smoke CI family consistently tops per-workflow consumption across the window, with the PR-review agents (Code Quality, Skills Reviewers, Sous Chef) forming a steady second tier. Day-to-day spikes track CI-heavy pushes rather than any single runaway workflow, and most lines sit well below the 30-day average total line.

---

🔗 GitHub REST API Calls Heatmap (90 days)

Weekday cells dominate — consumption clusters Monday–Friday and thins over weekends, consistent with development activity driving agentic runs. The mid-June band carries the darkest cells (the 574K peak), while several near-zero days (e.g. 2026-06-21, 844 calls) mark quiet weekends.

---

🍩 Top API Burners (24h)

Consumption is highly concentrated: Smoke CI alone is 42.3% of today's REST API quota and the top 3 workflows account for 55.7%. This concentration means a single misbehaving workflow can move the daily total substantially — worth watching given the Smoke CI reliability issue below.

---

🔗 GitHub REST API Consumption by Workflow (last 24h)

Smoke CI consumed 36,567 calls across 25 runs — and notably all 25 of those runs ended non-success, so a large share of quota is being spent on failing runs. No individual run breached the 15,000/hr core limit (the dashed reference marks the per-hour ceiling, not the 24h aggregate). Fixing Smoke CI would both recover quota and lift the overall success rate.

---

Top 10 Workflows by REST API Consumption (last 24h)

Workflow	REST API Calls	Runs	Avg Duration
Smoke CI	36,567	25	5.3m
Test Quality Sentinel	5,787	4	9.0m
Impeccable Skills Reviewer	5,752	4	9.3m
Tidy	4,631	5	13.0m
Design Decision Gate 🏗️	3,470	4	8.7m
Matt Pocock Skills Reviewer	3,443	4	10.2m
PR Sous Chef	3,351	5	10.4m
PR Description Updater	3,095	2	8.5m
PR Code Quality Reviewer	2,945	4	12.1m
Smoke Copilot - AOAI (Entra)	2,132	1	20.5m

---

Trending Indicators

• 7-day API trend: ↑ +15.2% vs. previous 7 days
• 30-day API trend: → (insufficient data — 57 of 60 required daily points collected)
• GitHub REST API call rate: ~99,677 calls/day over last 7 days (per-run hourly limit: 15,000)

---

⚠️ Reliability Watch

• Smoke CI failing en masse: 25/25 runs today ended non-success while consuming 42.3% of REST API quota. This is the single biggest driver of both the 69.6% success rate and today's API footprint. Recommend investigating the Smoke CI workflow before optimising anything else.
• Safe-output writes at 0: no issues/PRs/comments/discussions were actuated by monitored runs today (consistent with recent history) — expected for a CI/review-heavy day, but worth confirming the safe_items_count pipeline is populating correctly.

---

📦 Cache Memory Status

• Location: /tmp/gh-aw/cache-memory/trending/api-consumption/history.jsonl
• Cache restored from previous run: yes (56 existing entries)
• Collection mode: incremental
• Logs start_date used: -1d
• Data points stored: 57
• Earliest entry: 2026-05-18
• Retention policy: 90 days

🔎 Collection Notes

• The agentic-workflows logs tool timed out after 120s during download; 102 complete run summaries were written to disk and used as the authoritative dataset. ~170 additional run directories were left incomplete (no aw_info.json) and excluded.
• No continuation pages were requested (the initial call did not return a continuation before timing out).
• All 102 complete runs are dated 2026-07-16 UTC; the day is still in progress, so totals are a lower bound.

---

Automatically generated by the api-consumption-report workflow.

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• awmgmcpg

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "awmgmcpg"

See Network Configuration for more information.

Generated by 📊 GitHub API Consumption Report Agent · 277.2 AIC · ⌖ 37 AIC · ⊞ 11.9K · ◷

• expires on Jul 19, 2026, 3:43 AM UTC-08:00

[github-actions[bot]]

This discussion has been marked as outdated by GitHub API Consumption Report Agent.

A newer discussion is available at Discussion #46226.