(Related Issues Linked) Github Actions Failing After Sudden Billing Error: "account is locked due to a billing issue." #212276
Replies: 8 comments 10 replies
|
💬 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. ⭐ |
|
@github-staff if you see this we need help! @Blue-Paladin-Dev is suffering from this too |
|
Same thing happened to me as well |
|
Hey @ahmed33033 |




Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Other
Discussion Details
The Issue
GitHub Actions are failing after a billing issue suddenly surfaced, even after thousands of actions were executed without issue.
The full error message: "The job was not started because your account is locked due to a billing issue."
Related Issues
Many related issues have been reported in the past, but there seems to be an uptick in the last 24 hours.
Here are links to the latest ones:
Here are links to older ones:
Further Discussion
Yesterday, Github Actions seems to have encountered an incident, linked here: https://github.com/orgs/community/discussions/212173
This roughly coincides with when some of the linked actions (and my personal actions) have started failing due to the billing issue.
In addition to the many related issues, it seems many other users are impacted because my personal, CRON scheduled Github Action has been running almost exactly every 30 minutes for now. What's weird about that, you may ask? Cron'ed Github Actions are known not to run exactly on time, seemingly due to the huge uptick in usage load with the surge of GenAI. So, if they're suddenly running exactly on time, this is probably an indication that the load on GitHub Actions suddenly dropped, and I'm assuming that's due to the aforementioned billing issue.
All reactions