GitHub Actions budget is preventing further use: what to do
A spending limit on GitHub-hosted runners has been reached. Here is which one, how to get jobs running again, and how to keep it from happening.

When GitHub stops a job for money, the job never starts, and its annotation says:
The job was not started because an Actions budget is preventing further use.
It means a spending limit on GitHub-hosted runners has been reached. Nothing is wrong with the workflow. Here is which limit it is, how to get jobs running again, and how to keep it from happening.
Which jobs it stops
Only jobs that are paid for. GitHub’s Actions billing page lists two kinds of use that stay free and never touch your included usage:
- Standard GitHub-hosted runners in public repositories.
- Self-hosted runners.
So it stops jobs on GitHub’s runners in private repositories, and jobs on larger runners anywhere: “Larger runners are billed for public repositories.”
Why it happens
Every plan includes some Actions usage each month, now counted in dollars rather than minutes. From the same page:
| Plan | Included each month | On the standard Linux runner |
|---|---|---|
| GitHub Free | $12 | 2,000 minutes |
| GitHub Pro | $18 | 3,000 minutes |
| GitHub Free for organizations | $12 | 2,000 minutes |
| GitHub Team | $18 | 3,000 minutes |
| GitHub Enterprise Cloud | $300 | 50,000 minutes |
The minutes are at $0.006, the standard Linux runner’s price. Windows, larger and macOS runners use it up faster. Once it is used, one of two things stops the jobs:
- No payment method. “If your account does not have a valid payment method on file, usage is blocked once you consume the included compute usage.”
- A budget with “Stop usage when budget limit is reached” turned on has been spent. Budgets can be set for the whole account, an organization, a repository, a product (Actions) or one runner type, and GitHub’s budgets guide warns that they stack: when any one of them that stops usage is spent, use is blocked, even if another budget still has room.
That second case catches teams out. An organization with a $50 budget for Actions and a $100 budget for one runner type is blocked when the $50 runs out, and the guide’s own example says the larger budget “cannot prevent this block and should be deleted”.
Get jobs running again
- Find the budget. Open your billing settings, or the organization’s, and choose Budgets and alerts. The spent budget is the one at 100%.
- Raise it, or let it alert instead of stop. Edit the budget and raise the amount, or clear Stop usage when budget limit is reached. Without it, the guide says, “you will be notified by email if you exceed your budget, but usage will not be stopped.”
- Add a payment method if the account has none.
- Re-run the refused jobs from their run’s page.
The included usage resets at the start of each billing cycle, so waiting also works, if the jobs can wait.
Keep it from happening
- Turn on alerts. A budget can email at 75%, 90% and 100%, and the included usage at 90% and 100%.
- Use one budget for Actions, not overlapping ones for the product, a runner type and a repository.
- Spend fewer minutes. Cancel superseded runs with
concurrencyandcancel-in-progress: true, skip workflows for changes that cannot affect them withpaths, and cache dependencies. - Move the heavy jobs off GitHub-hosted runners. Jobs on your own runners are not charged by GitHub, so no Actions budget can stop them.
With SuperCI
SuperCI, which we make, runs GitHub Actions jobs on fresh machines in your own AWS, Cloudflare or Modal account, as self-hosted runners. You pay your cloud’s price and nothing to GitHub for them: on an AWS spot machine, 4 CPUs come to about $0.0014 a minute against GitHub’s $0.012 (see the calculator).
jobs:
test:
runs-on: superciSuperCI has spending limits of its own: a monthly budget for each provider, and limits for the month and the day across all of them. A provider over its budget passes jobs to the next one in your order, so a job still runs somewhere you allowed.
Related: what a GitHub Actions minute costs, and every GitHub Actions limit in one place.