Actions Usage Metrics stopped recording new data around July 21, 2026

[daande]

🏷️ 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.

[github-actions[bot]]

💬 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 ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

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. ⭐

[ThoratSoham]

I see multiple accounts reporting the same problem
If you have git hub enterprise, then you can create a ticket and tell them about your problem, or If you need to verify or report current Actions consumption for billing/management while the web dashboard is frozen:

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>"
-H "Accept: application/vnd.github+json"
https://api.github.com/orgs/{org}/settings/billing/actions

[mhmdwaelanwr]

Since the workflows themselves are still running and consuming minutes, I would first use the CSV export from Insights → Actions → Usage Metrics to determine whether this is only a dashboard rendering problem or whether the underlying metrics dataset is stale as well.

GitHub's documentation says the current-week/current-month views include data through the current day, and usage metrics are intended to report workflow/job minutes. The main documented exclusions are skipped runs and runs that consume zero minutes.

I would check:

1. Export the same date range as CSV.
2. Compare a few workflow runs after July 21 that definitely consumed GitHub-hosted runner minutes.
3. Remove any filters and compare organization-level versus repository-level Usage Metrics.
4. Check whether Performance Metrics are continuing to receive newer runs.

If the CSV is also frozen at July 21 while billable workflow runs after that date exist, that strongly suggests a metrics ingestion/backend problem rather than a browser or dashboard-filter issue.

In that case I would open a GitHub Support ticket and include:

• organization name;
• ast date visible in Usage Metrics;
• IDs/URLs of several workflow runs after that date;
• screenshots of the dashboard;
• the exported CSV showing the same cutoff.

I would not change the workflows themselves, because the workflow execution path appears healthy — the failure is isolated to reporting.

If the CSV contains newer data but the dashboard does not, then the problem is narrower and looks like a UI/query issue instead.