Replies: 2 comments
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
|
I see multiple accounts reporting the same problem Organization Billing UI: Go to Organization settings → Billing & licensing → actions to see current overall minute consumption. GitHub REST API: Query the Billing API endpoint to pull raw usage data programmatically: curl -H "Authorization: Bearer <YOUR_TOKEN>" |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Metrics & Insights
Discussion Details
What's happening
Since around July 21–22, 2026, the organization-level Actions Usage Metrics dashboard (Insights → Actions → Usage Metrics) has stopped showing new data. The most recent data point is on/around July 21; nothing has populated since, even though workflows are still running normally and consuming minutes as expected.
Expected
Usage Metrics should continue to update daily to reflect ongoing Actions consumption.
Actual
The dashboard appears frozen at ~July 21, 2026 — no new usage data is being recorded/displayed after that date. Actions themselves run fine; only the metrics/insights reporting seems affected.
Environment
GitHub Enterprise Cloud organization
Viewing via Insights → Actions → Usage Metrics in the web UI
Questions
Is anyone else seeing Actions Usage Metrics stop updating around the same date (July 21, 2026)?
Is this a known issue / is there an incident tracking it?
Happy to provide more detail privately via Support if helpful.
All reactions