Fix: an Actions budget is preventing further use (2026)

GitHub shows this when it won't bill more Actions usage: a budget set to stop usage is spent, the included usage is gone and no payment method is on file, or a payment failed. An owner fixes it in Billing & Licensing. Jobs on a self-hosted runner, such as Skipbox, don't draw on the budget.

Fluxenic, the company behind Convika, makes Skipbox, so one way out on this page is our own product. Every GitHub fact below is quoted from GitHub's own pages, read November 11, 2026 (Japan time) and linked under Sources.

• A budget is spent. A budget that covers Actions has Stop usage when budget limit is reached turned on. An organization owner raises it or turns the stop off.
• No payment method. The plan's included usage is used up and the account has no valid payment method. An owner or billing manager adds one.
• A payment failed. A declined card or a failed authorization hold locked the account's billing. An owner or billing manager updates the payment method.
• To run the jobs today: move them to a self-hosted runner. Skipbox is a managed one: change the job's runs-on: line to skipbox.

The two messages, as GitHub shows them

GitHub's docs don't print either message. People who hit them quote them like this:

• "The job was not started because an Actions budget is preventing further use." A developer quoted it in a post of December 28, 2025, after his deploys stopped.
• "The job was not started because recent account payments have failed or your spending limit needs to be increased." An organization quoted it in GitHub's community forum on July 20, 2025.
• "The job was not started because your account is locked due to a billing issue." Quoted in the forum on November 6, 2026, in a thread that links 14 similar reports.

"Spending limit" is the old name for a budget: GitHub's old page on managing your spending limit for GitHub Actions now redirects to its guide on setting up budgets.

The mechanism behind all three is in GitHub's docs:

• "For metered products such as GitHub Actions, Copilot AI credits, or cloud sandboxes, you can set budgets to prevent usage once the budget threshold is reached."
• "If your account does not have a valid payment method on file, usage is blocked once you consume the included compute usage."
• "Your account's paid features are locked if your payment is past due because of billing problems."

The three causes, and who can fix each

On who edits an organization's budget, GitHub's pages disagree. Its setup guide says: "As the owner of an enterprise or organization account, or as a billing manager, you can set a budget." Its billing manager page lists only "View organization-level budgets." If you are a billing manager and see no edit control, ask an organization owner.

Fix 1: raise the budget, or turn off the stop

For an organization, as an owner:

1. Click your profile picture, then Your organizations, then Settings beside the organization.
2. Under Access in the sidebar, click Billing & Licensing, then Budgets and alerts.
3. Find every budget that covers Actions. GitHub: "Each row shows the budget's scope, spending against the budget amount, and status."
4. Open the menu beside the spent budget and edit it.
5. Raise the amount, or clear Stop usage when budget limit is reached. Without the stop, GitHub says, "you will be notified by email if you exceed your budget, but usage will not be stopped."

For a personal account, open github.com/settings/billing and click Budgets and alerts. For an enterprise, Billing & Licensing is a tab at the top of the enterprise page.

Look for a second budget. Budgets overlap, and one spent budget is enough: "Usage of metered products can count toward multiple applicable budgets at the same time, and if any budget with Stop usage when budget limit is reached enabled is exhausted, additional usage is blocked."

GitHub's own example is an organization with a $50 budget for the Actions product and a $100 budget for one runner SKU. Once the $50 is spent, "members are now blocked from using all GitHub-hosted runners until the next billing cycle or until the budget is increased," and "The overlapping $100 SKU budget cannot prevent this block and should be deleted."

Fix 2: add a payment method

Once the plan's included usage is consumed, GitHub bills the rest "using the payment method set up for your GitHub account." With none on file, jobs stop instead.

1. Open the account's Billing & Licensing pages.
2. Click Payment information.
3. In Payment method, click Edit and add a card or PayPal.
4. Open Budgets and alerts and check the Actions budget. A budget of $0 with the stop on still blocks paid usage, whatever card is on file.

What each plan includes, and what a minute costs past it, is in GitHub Actions pricing in November 2026.

Fix 3: clear a failed payment

GitHub on a declined card: "we'll send you an email about why the payment was declined. You'll have a few days to resolve the problem before we try charging you again."

1. Read that email for the bank's error message.
2. Open Billing & Licensing → Payment information and update the payment method.
3. Wait for the charge. GitHub: "The account will automatically unlock when a payment has been successfully processed. Payments may take up to 24 hours to process."

A lock can come without any plan to pay. GitHub's docs: "A failed authorization hold when you try to sign up for Copilot or increase a budget can also lock your personal account billing and block GitHub Actions or other free-tier access. This can happen even if you plan to stay on GitHub Free."

If the billing pages show nothing to fix, GitHub says to "contact us through the GitHub Support portal to request a review of the billing lock." In the July 2025 forum thread, the organization had raised its budget and found no failed payments, and the message stayed. Its author wrote the next day: "I opened a support ticket, and after manually syncing, everything is working perfectly now."

Re-run the refused jobs

A fix lets new jobs start. It doesn't start the ones GitHub already refused.

1. Open the failed workflow run.
2. In the upper-right corner, open Re-run jobs and click Re-run failed jobs.

GitHub allows this "up to 30 days after its initial run." A scheduled workflow runs again at its next scheduled time.

When the block lifts on its own

A spent budget blocks "until the next billing cycle or until the budget is increased." For metered products such as Actions, the billing period "starts at 00:00:00 UTC on the first day of each month." The included usage "resets to the full amount at the start of each billing cycle."

So a budget block and a used-up allowance both lift on the 1st at 00:00 UTC. A failed payment doesn't lift by date. It lifts when a payment goes through.

Run the blocked jobs today on a self-hosted runner

A spent budget stops GitHub's own machines. GitHub's example says members are blocked from "all GitHub-hosted runners." Self-hosted runners aren't billed: GitHub's billing page lists "Self-hosted runners" as usage that "remains free independently and does not reduce the included compute usage." A job that runs on one adds nothing to an Actions budget.

To move one job to Skipbox:

1. Sign in at skipbox.dev with GitHub. Install the Skipbox CI app on your organization, or Skipbox (personal) on your personal account.
2. Change the blocked job's runs-on: line to skipbox and push.
3. The trial runs one 4 vCPU job at a time, for 7 days or 3,000 job-minutes from your first job, whichever comes first.

Start a free Skipbox trial on skipbox.dev

What stays where it is:

• macOS, Windows, and Arm jobs. Skipbox runs Linux x64 jobs on Ubuntu 24.04. The rest stay on GitHub's runners and stay blocked until the budget or the payment is fixed.
• Public repositories' jobs on standard runners. GitHub doesn't bill them, so a budget never blocks them. Move them to Skipbox for speed, not to get past the budget.
• An account locked for a billing issue. GitHub's docs don't say whether a locked account's jobs start on self-hosted runners. Fix the payment first.

Other runners at a fixed monthly price are in flat-rate GitHub Actions runners.

Keep it from coming back

• One hard budget for Actions. GitHub's advice: "avoid creating overlapping budgets for the use of a product and a SKU, or an organization and a repository, so that users are not unexpectedly blocked from using a feature that they rely on."
• Budget alerts. On the budget, select Receive budget threshold alerts. GitHub emails and shows a banner at 75%, 90%, and 100%.
• Included usage alerts. On Budgets and alerts, select Receive alerts when my included usage reaches 90% and 100%. You hear before paid usage starts.
• A new budget counts late. A budget "applies only to metered usage from the date of its creation onwards," so its first month can run past it.
• A fixed price for the heavy jobs. A job on a flat-price runner costs the same in a busy month, and no budget is involved. How many minutes each plan's included usage buys is in are GitHub Actions free for private repositories.

Related reading

• GitHub Actions runner prices compared: GitHub, faster runners, and self-hosting
• Are GitHub self-hosted runners free? Yes, in 2026
• AI coding agents and your CI bill: the GitHub Actions math
• Claude Code on GitHub Actions: what the minutes cost and how to cap them

Frequently asked questions

What does "The job was not started because an Actions budget is preventing further use" mean?

A budget that covers GitHub Actions has Stop usage when budget limit is reached turned on, and it is spent. GitHub's docs: "if any budget with Stop usage when budget limit is reached enabled is exhausted, additional usage is blocked." An owner raises the budget or turns the stop off, then re-runs the failed jobs. Jobs on a self-hosted runner, such as Skipbox, don't draw on the budget. Fluxenic, the company behind Convika, makes Skipbox.

Who can raise a GitHub Actions budget?

An organization owner, for the organization's budgets. An enterprise owner or billing manager, for enterprise and cost center budgets. The account's owner, on a personal account. The control is in Billing & Licensing → Budgets and alerts. GitHub's billing manager page lists only viewing an organization's budgets, so a billing manager who can't edit one asks an owner.

Do self-hosted runners count against the Actions budget?

No. GitHub's billing page lists self-hosted runners as usage that "remains free independently and does not reduce the included compute usage" (read November 11, 2026). GitHub's example of a spent budget blocks "all GitHub-hosted runners." A job whose runs-on: points at a self-hosted runner adds nothing to the budget.

How do I keep GitHub Actions running when the budget runs out?

Raise the budget, or move jobs to a runner GitHub doesn't bill. Skipbox is a managed self-hosted runner at a fixed monthly price: $39, $79, or $149 a month for 4, 8, or 16 vCPU, with unlimited minutes. Its jobs add nothing to an Actions budget, so a spent budget can't stop them. Changing a job's runs-on: line to skipbox moves it. Skipbox runs Linux x64 jobs.

I raised the budget. Why are my jobs still not starting?

Three things to check. Re-run the failed jobs: GitHub doesn't restart jobs it refused. Look for a second spent budget on a repository, a SKU, a cost center, or the enterprise. Then open Payment information for a failed charge. If all three are clean, contact GitHub Support.

When does the block lift on its own?

A budget block lifts at the next billing period, which for Actions "starts at 00:00:00 UTC on the first day of each month." The plan's included usage resets to the full amount at the same moment. A block from a failed payment lifts when a payment is processed, which GitHub says can take up to 24 hours.

Sources

Read 2026-11-11 (Japan time).

• GitHub Docs: Setting up budgets to control spending on metered products: overlapping budgets, the $50 example, the stop option, the steps, who can set a budget (checked 2026-11-11)
• GitHub Docs: Budgets and alerts: stopping usage, roles, alerts, a budget's first billing cycle (checked 2026-11-11)
• GitHub Docs: GitHub Actions billing: usage that remains free, blocking without a payment method (checked 2026-11-11)
• GitHub Docs: Actions runner pricing (checked 2026-11-11)
• GitHub Docs: Billing cycles (checked 2026-11-11)
• GitHub Docs: Troubleshooting a declined credit card charge (checked 2026-11-11)
• GitHub Docs: a locked account (checked 2026-11-11)
• GitHub Docs: Adding a billing manager to your organization (checked 2026-11-11)
• GitHub Docs: Re-running workflows and jobs (checked 2026-11-11)
• GitHub Docs: Self-hosted runners (checked 2026-11-11)
• GitHub Community #166876: GitHub Action Failing Despite Adding Budget Amount (2025-07-20, checked 2026-11-11)
• GitHub Community #212276: Actions failing after a billing error (2026-11-06, checked 2026-11-11)
• Luca Berton: GitHub Actions is great, until you hit the budget wall (2025-12-28, checked 2026-11-11)
• Skipbox: plans, unlimited minutes, the trial, private repositories (checked 2026-11-11)