GitHub-hosted Actions blocked despite healthy billing #205214
Replies: 3 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. ⭐ |
|
that exact message is an entitlement gate before a hosted runner is assigned, which matches what you’re seeing (zero steps, self-hosted still works). the billing UI looking healthy does not always mean Actions is allowed to spend. two things get mixed up a lot:
hosted jobs die if the Actions spending limit is $0 / not enabled, even when a budget exists and cards look fine. do this first (the owner of the repo, not some other org) Settings → Billing → Spending limits (not Budgets)
quick api check from the billed account: # billed account login (user or org)
gh api user/settings/billing/actions
# or for an org:
gh api orgs/YOUR-ORG/settings/billing/actionslook at if spending limit is already on and > $0 usually a stale billing-entitlement flag. common leftover:
workaround that sometimes unsticks it without waiting on support: change the Actions spending limit by $1, save, change it back. that forces a re-check. if that still leaves hosted jobs at “not started”: yes, this one is a manual billing-entitlement sync. support needs:
self-hosted working is expected here - that path never hits the hosted-minutes meter. |
|
The fact that self-hosted runners work while every GitHub-hosted runner fails before assignment is a strong clue. Since you've already checked successful payments, the Actions budget, and the spending limit, I'd focus on whether the billing or entitlement state associated with the account is out of sync. One additional check would be to confirm which account or organization owns the repository and which billing entity is responsible for its Actions usage. If those match the budget you've checked, I'd open or update a GitHub Support ticket with the exact failure message, affected run IDs, billing screenshots with sensitive information removed, and confirmation that self-hosted runs succeed. I wouldn't keep changing runner labels or workflow steps because the failure occurs before the job reaches a runner. |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Actions Runner
Discussion Details
All GitHub-hosted Actions jobs fail before runner assignment with zero steps and this message:
Billing shows successful payments, an Actions budget of $1,800 at 56%, and Stop usage disabled. ubuntu-latest, ubuntu-slim, and macOS are all affected, while self-hosted jobs work.
Has anyone had this resolved through a manual billing-entitlement sync by GitHub Support?
All reactions