# GitHub Actions: job not started (billing)

> Getting the error “GitHub Actions job not started” because of billing? Here is how to fix it. A payment failed, or the spending limit is too low.

**GitHub Actions: job not started (billing).** GitHub didn’t start the job because of a failed payment or a spending limit. On private repositories, macOS runners use minutes ten times faster than Linux ones.

- GitHub Actions. GitHub Actions has no minutes left.
- Interactive page: https://capwr.app/free-tools/build-error-explainer/github-actions-billing
- Build error explainer: https://capwr.app/free-tools/build-error-explainer
- Last updated: 2026-10-03

## What this error means

GitHub didn’t start the job because of a failed payment or a spending limit. On private repositories, macOS runners use minutes ten times faster than Linux ones.

## Why it happens

GitHub refused to start the job. The account’s payment failed, or the Actions spending limit is too low for the minutes this run needs. On private repositories, macOS minutes cost ten times a Linux minute.

## The message tools print

```
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.
```

## How to fix it

1. Check Billing and plans in your GitHub account or organization settings.
2. Raise the Actions spending limit or fix the payment method, then re-run the job.

## Check a log that shows this

Paste the failing step into the [build error explainer](https://capwr.app/free-tools/build-error-explainer). It matches this message, and any others in the same log, in your browser. Nothing is uploaded.

## Other GitHub Actions errors

- [Resource not accessible by integration](https://capwr.app/free-tools/build-error-explainer/resource-not-accessible-by-integration)
- [GitHub Actions job exceeded the time limit](https://capwr.app/free-tools/build-error-explainer/github-actions-exceeded-maximum-execution-time)
- [Input required and not supplied](https://capwr.app/free-tools/build-error-explainer/input-required-and-not-supplied)

## Read the whole failed ship, not the last line

When a CapWrapp ship fails, open it in History and choose Explain with AI. That reads the whole build log.

[Get started free](https://capwr.app/login).

## About CapWrapp

CapWrapp turns a web app on GitHub — built with Lovable, Bolt, Base44, Cursor or by hand — into iPhone and Android apps. It adds Capacitor if the repo needs it, signs the builds, and ships them to TestFlight and Google Play from GitHub Actions, with no Mac or Xcode on your side. [Get started free](https://capwr.app/login) · [Lovable to App Store guide](https://capwr.app/guides/lovable-to-app-store)