GitHub Actions "billing: spending limit reached for Actions"

Distinct from running out of included minutes, this stops jobs because your explicit Actions spending limit has been hit. GitHub will not bill past the cap, so it blocks new metered usage until you raise it.

What this error means

Jobs stop starting partway through a billing cycle and the billing page shows the Actions spending limit is reached.

billing: spending limit reached for Actions
The job was not started because the Actions spending limit for this account has been reached.

Common causes

Hard spending cap configured

An admin set a finite Actions spending limit; once metered overage reaches it, GitHub blocks further usage.

Unexpected overage from costly runners

macOS/Windows or larger runners burned through the cap faster than anticipated.

How to fix it

Raise or remove the spending limit

1. Open Settings > Billing and plans > Spending limits.
2. Increase the Actions limit or set it to unlimited.
3. Re-run the blocked jobs.

Cut overage drivers

1. Audit which workflows consume the most paid minutes in the usage report.
2. Shift expensive jobs to Linux or to managed runners that bill your own compute outside GitHub metering.

How to prevent it

• Set alerts well below the spending limit so the cap is not a surprise.
• Review the monthly Actions usage report for runaway workflows.

Related guides