Replies: 6 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. ⭐ |
|
Update with a likely root cause, to help route this to the right team. Our lock matches the default $1,000 spending limit bug that GitHub staff (nebuk89) described on Oct 22, 2026 in community discussion #199036 ("an edge case appeared that locked your org to a $1k spending limit"). Other orgs in that thread were locked at $1,005.75 with a $1,500 budget and $1,006.48 with a $1,350 budget. We were locked at $1,004.69 with a $1,200 budget, and raising the budget to $2,500 changed nothing. This is not a payment problem: payment history is all successful, nothing is past due, and the card was re-saved. Actions is the only product with usage this month, so no other budget is involved. Request: please check whether rep-wallet is still pinned to a default $1,000 Actions limit and remove it, or escalate to the billing engineering team that handled that bug. We posted our details in discussion #199036 as staff requested there. Still refused as of 17:00 UTC Nov 15. All GitHub-hosted CI for our team is down. |
|
Hi @slappertx, This definitely looks like something GitHub needs to investigate on the billing side. What's interesting is that you've already increased the Actions budget, confirmed that all payments were successful, and updated the payment method, yet the jobs are still being blocked. That makes a normal budget exhaustion or payment failure less likely. Your observation about the $1,000 threshold is also worth looking into, especially considering the similar issue reported in [Discussion #199036](https://github.com/orgs/community/discussions/199036). I would suggest asking GitHub Support to specifically check whether the internal Hopefully, a GitHub staff member can look into ticket #5008284 and escalate it to the billing engineering team. One thing I'd really like to know: have you received any response from GitHub Support confirming whether this is the same issue as #199036? Relevant documentation: |
|
Same symptom here, beginning 2026-11-09. Support ticket 4979788 — three detailed updates since, and no response from GitHub of any kind What matched your report exactly, while we were still on GitHub-hosted runners:
How it ended for us, which is the part I think is worth knowing here: it was never resolved and we On your escalation request: this is not a few isolated accounts. The same symptom is open across at So, adding our ticket to your ask: could this be escalated to the billing engineering team that |
That's crazy. No reply from support!? I think we are going to Self-hosting Gitea (https://about.gitea.com/) on an AWS. I think we have outgrown GitHub's problems and that's the next logical step |
|
My org is stuck in this nightmare. We also ran up a bill to $1008 and now can't run CI. What makes it a nightmare is the radio silence from support for over a week now and no way to escalate. They aren't even pretending to care. I guess its a lesson we learn the hard way. We can't have a vendor this unresponsive be anywhere close to a critical processes. Petty of me but I wish my $1500 a month would sting at least a little. Its not even enough to be a rounding error. |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Other
Discussion Details
Since early this morning (Nov 15, 2026) every GitHub Actions job in our organization's private repository is refused before it starts. The job annotation says:
What we have already checked:
The refusals began right after our monthly metered Actions usage crossed a round dollar amount, which suggests an account-level billing lock rather than the budget. GitHub's support form also describes this as a possible "billing lock".
We opened support ticket #5008284 (Billing > Actions billing). Since our plan only has standard support, it will likely sit until Monday, and our whole team's CI is blocked.
Could a GitHub staff member please look at ticket #5008284 and clear the hold, or tell us what is triggering it? Has anyone else seen this message without a failed payment or reached budget, and what fixed it for you?
Related: https://github.com/orgs/community/discussions/166876
All reactions