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

This is a really concerning bug, especially since your budget screen explicitly shows the cap was set correctly and "Stop usage" was active. Blowing past a hard limit by over $400 defeats the entire purpose of setting a budget.

To answer your questions based on how GitHub's metered billing engine usually processes endpoints:

Why it exceeded / Delayed enforcement: GitHub's billing pipeline processes API and token usage in background batches rather than a real-time, synchronous stream. If a high volume of concurrent automated requests (or massive agent loops) hit the API within a short window, the usage can outrun the pipeline's latency before the "stop" flag is triggered.

What you will be billed / Refund: Because your dashboard clearly proves you had a hard block enabled at $710, you have a rock-solid case for a billing adjustment. GitHub shouldn't hold you liable for an enforcement sync delay on their backend.

Definitely open an urgent billing ticket directly with GitHub Support and attach these exact screenshots. Their billing team is usually very understanding with budget enforcement failures and should be able to issue a credit or refund for the overage.

(If this explanation helps clarify the pipeline delay and gives you a path forward for the refund, please feel free to mark this response as answered!)

Worth checking the budget creation date before assuming enforcement failed. Per GitHub budget documentation, a budget only counts metered usage from the moment it is created, so anything consumed earlier in the same billing cycle sits on the billing overview but is invisible to that budget.

The numbers fit that. 1,145.45 total metered against 688.94 counted by the budget leaves about 456 unaccounted for, and the budget page is sitting at 97 percent rather than over 100. If stop usage had genuinely failed, the budget own Spent figure should have run past 710 as well. It did not, which points at the two figures covering different windows rather than at the block never firing.

The other thing worth ruling out is SKU scope. The budget is set to All AI Credit SKUs, so any other metered product on the account (Actions, Codespaces, Packages, Git LFS) accrues on the billing overview without ever touching it.

The detailed usage report export should settle it, since it breaks usage down per user, per day and per SKU. Filtering either side of the budget creation date shows straight away whether the gap is pre-budget usage, a different SKU, or a real enforcement miss. More on how these controls interact: https://olumia.dev/blog/github-copilot-spending-limit