Actions blocked at ~$1,000 metered usage despite $1,500 budget and no failed payments (Ticket #5025330) #213641
Unanswered
fbosetti-ac
asked this question in
Actions
Replies: 1 comment
|
💬 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. ⭐ |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Actions Runner
Discussion Details
Hi everyone!
Our organization's GitHub Actions jobs have been completely blocked since Nov 18 at 18:44 UTC with the following error annotation on every run:
"The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the ‘Billing & plans’ section in your settings"
What we've verified:
• Trigger point: Workflows ran normally until our November metered usage crossed $1,000 (~$1,023 gross / $1,010 billable).
• Budget settings: Our Actions budget is set to $1,500 with "Stop usage when budget limit is reached" disabled.
• Payment status: Every invoice in our Payment History shows "Success", there is no balance due or "Pay now" button in Billing Overview, and replacing our payment method on Nov 18 did not lift the block.
• Plan: GitHub Free organization.
It looks like our account hit an internal $1,000 unbilled metered usage threshold/hold that requires manual clearance from Billing support, as there is no way to trigger a mid-cycle payment from the UI.
We opened support ticket #5025330 2 days ago, as this is currently blocking our production deployments and database migrations. Could a community moderator or GitHub staff member help flag this ticket for Billing review?
Thanks in advance for any help!
All reactions