Actions won't run after increasing budget

[mattschutt]

Why are you starting this discussion?

Question

What GitHub Actions topic or product is this about?

Actions Runner

Discussion Details

We ran out of actions and hit the

"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"

message in our PRs. No problems, we increased our budget.

However, they still won't run. They fail with the same message. Billing is set up, we get our monthly bills, budget is there but these things won't run.

Any help/tips would be appreciated.

[codedbysoumyajit]

Hey, we ran into this exact issue recently — increasing the budget alone didn’t do the trick right away.

What worked for us was going into Billing & plans > Spending limits and explicitly raising the spending limit and confirming it. Sometimes the UI shows the new limit, but it's not actually confirmed or saved properly.

Also worth checking:

Make sure there are no outstanding failed payments under Billing > Payments.

Try triggering a workflow manually to see if that nudges it.

If all else fails, GitHub Support was super responsive when we reached out — they fixed it within a few hours.

Hope that helps! Let me know if it gets sorted.

[mattschutt]

Probably worth noting this is for a business account

I bumped up our Actions budget again but it didn't change anything. Updated the payment information -- changed it rather. It was still good. No outstanding/failed transactions. Opened new PRs, closed and reopened the failed one -- all fail still. Same message:

"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"

The budget UI shows a 0% used branch of my new set budget.

I wish I had your luck with GitHub support -- it's been over a week since I opened a ticket with them and I haven't heard anything! Thus, this post! :). Thanks for the help!

[eureka-cpu]

Just opened a ticket about this, did it eventually start working again @mattschutt ?

[chris-griffin]

Seems like a GitHub Bug. We ran into this issue. We increased the Organizational limits for Actions to ensure it had plenty of budget left. Despite having no failed payments we were seeing "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".

I turned off the "Stop usage" option for the Actions Organization budgets just now and that seems to have done the trick. I haven't yet tried turning that back on to see if it would cause the same issue.

[eureka-cpu]

In our case we were able to fix it by setting the org wide budget as well as a per-project budget for action runners.

Hope this helps someone else!

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬