The job was not started because recent account payments have failed

[flornet]

Select Topic Area

Question

Body

I've been using Github Pages for a few years now.
Suddenly, building & deploying my site with Github Actions stopped working.
The message is:
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'm using a free account.
One week ago, it was working... I really don't get it.
The only recent change is that I started using Co-pilot today within Visual Studio Code.
Could it be the cause of this problem?
Any idea on how to fix it?

Cheers,

Florent

[zapta]

Same here. With very low workflow usage.

[keshav-sudo]

This error isn’t caused by GitHub Copilot — it’s related to GitHub Actions billing/limits.

Even on a free account, GitHub Actions comes with a limited number of free build minutes and storage (500 MB for artifacts/logs, and a quota of minutes depending on your plan). When you exceed those limits or if there’s a billing issue, Actions jobs stop running and you see the exact error you mentioned.

What you should do:

Go to Settings → Billing & plans in your GitHub account.

Check if there are any failed payments or if your Actions usage has exceeded the free quota.

If usage is exceeded, you need to add a payment method and set a spending limit (you can even set it to $0 if you don’t want to allow extra charges).

If you don’t want to add billing, you’ll need to wait until your monthly quota resets (on the first day of the next month).

As a workaround, you can also build your site locally and push the static files directly to the gh-pages branch instead of relying on Actions until your quota resets.

[flornet]

I've tried to add a credit card and it seems to work (although the limit stays at 0.0$)

[glandium]

Same here, although I totally could believe I've hit the limit of 2000 action minutes... but "Usage this month" under "Billing and plans"/"Plans and usage" shows ... 0 usage. At all. Which is also impossible.

[johnkerl]

Oddly single-cell-data/SOMA CI runs OK; single-cell-data/TileDB-SOMA CI fails as described here.

Weird since billing is per-org not per-repo.

Began about an hour ago and is now persistent.

[andychu]

I'm also hitting this, it seems like a bug, because our repo is public

In oils-for-unix/oils

[zapta]

I got this

"
GitHub (GitHub Support)Feb 20, 2025, 9:52 PM UTCHi there,Thanks for reaching out, and sorry for the trouble here. This appears to be related to a change that the Actions team made earlier today that had unintended consequences.They've reverted the change and you should be able to try this again without seeing an error. Please try that when you have a moment and let us know if you continue to see the error message, or if we can help with anything else at the moment.Cheers,TJ | GitHub Support
--"

[kangah-codes]

+1 None of my actions will run still

[LyuJiayi654]

+1 None of my actions will run still

[CeeRoo]

For those who may still be seeing an issue, our account owner had to set a monetary value for a budget. It had been set to 0 which was causing the deployment errors, but it was set to 0 for a long time. Not sure if anything changed at github with regard to deployments, but setting a budget value may fix it for you.

As a sidenote, the error message should be much clearer and point to the budget if that is the issue.

[Hassan-Zubair10]

Update: Filed a ticket on https://support.github.com and they resolved my issue.

[hudsonrio]

For those who may still be seeing an issue, our account owner had to set a monetary value for a budget. It had been set to 0 which was causing the deployment errors, but it was set to 0 for a long time. Not sure if anything changed at github with regard to deployments, but setting a budget value may fix it for you.

As a sidenote, the error message should be much clearer and point to the budget if that is the issue.

This helped us resolve our issue. Thanks @CeeRoo

[mikeelindsay]

Still having the issue

[bjorn-avans]

Facing the same problem as of today.

[nebuk89]

Let me check whats going on and follow up <3 sorry folks.

[andrii-bodnar]

Experiencing the same error in multiple public repositories (for example, https://github.com/crowdin/github-action/actions)

However, the last payment was successful and the current usage of GitHub Actions does not exceed 3000 minutes.

[philjackson]

We're (Pitch) also experiencing this. @nebuk89 did you find anything in your investigations?

edit: we're seeing it with a private repo on the team plan, all payments up-to-date that I can see.

[sebgie]

Also need to bump this thread. Private repos on the team plan fail. Invoices are all settled and spending limit is not reached.
No response from Support either.

[philjackson]

I've had a response from support, but quite a generic "we'll pass it onto the team". I'll update here if I hear anything else.

[sebgie]

Thank you for the update!
The team informed me just now that the builds are running again.

[brentmn]

We're having the same issue. Private repos, plenty of quota and spending limit available.

[brentmn]

Update: just started working again

[cherriford]

Also experiencing this on a public repo in a newly created organization

[rodriguezrebecca301-ops]

This issue usually comes up when billing details need updating or a recent payment didn’t go through. Resolving payment status quickly helps avoid service interruptions. Clear status tracking is important everywhere—just like students can easily https://webgradecalculator.com/ and stay informed without confusion.

[Mr-mohamed45]

How to Fix It

Go to Settings → Billing & plans:

Make sure your billing info is up-to-date.

Even on a free plan, GitHub sometimes needs a valid credit card on file to verify identity for usage limits.

Check your GitHub Actions usage:

Settings → Billing → GitHub Actions.

See if you hit the monthly free limit.

If you just enabled Copilot:

You might need to accept Copilot terms and add billing info to keep Actions running.

Once billing info is confirmed, rerun your workflow, and it should work again.

[jonathangkoehn]

Same problem here and I absolutely have more premium requests and the billing information has not changed. What is so hard is frustrating is it is almost impossible to report this easily to Github.

[dantaylorseo]

Just to leave a comment for everyone on here what solved it for me:

There's 2 elements to GitHub Copilot Agent - The Premium Requests and Action Minutes.

You need to make sure you have BOTH request and minutes available, either through free/included or by changing budgets.

If you are working in an organisation check that you have remaning minutes/budgets on the organisation too. The requests seem to come from your personal, but minutes from the org.

[jonathangkoehn]

This helped and was the problem on my end. Even though I do most through personal, our organization needed payment info even though it seems not to collect payments from it. How very odd.

[Biswajit-sow]

Meaning (Simple Explanation)

This error means your CI/CD pipeline (GitHub Actions, GitLab CI, Vercel, Netlify, CircleCI, etc.) refused to run the job because your billing failed — usually due to:

expired debit/credit card

insufficient balance

incorrect card info

auto-renewal payment failure

unpaid invoices on the account

The system blocks new workflow jobs until billing is cleared.

🛠 How to Fix It

1. Update your payment method

Add a working payment method (card, UPI, PayPal depending on the platform).

2. Clear outstanding invoices

Go to Billing → Invoices → Pay manually.

3. Retry the workflow/job

After updating payment, rerun:

GitHub: “Re-run all jobs”

GitLab: “Retry”

Vercel/Netlify: “Deploy Again”

4. If using a Student/Education account, verify it again

Some platforms revoke free benefits if not renewed.

One-Line Explanation

Your workflow didn’t start because your account’s recent billing attempt failed, and the platform blocks CI jobs until payment is updated or outstanding invoices are cleared.

[jonathangkoehn]

This seems to be for users that have Personal under an Organization or both so both accounts need checked for Billing. Now my Organization is getting billed for Actions...

[justin-basd]

I'm going to outline everything we have tried:

In our Organization Settings:

• Change billing address multiple times
• Change Actions budget multiple times, ensure headroom
• Add payment card details, remove it and added a different card
• Paid for Team tier for a year (which allegedly gives us GitHub Support via email) and ensure we have enough seats
• Downgraded to Free tier to see if that works

In my personal GH account:

• Add billing address
• Add payment card details
• Add Action limits

We cannot run any action in any organization repo. Wether the action was created via /.github/action.yml or through the Github UI. Wether its triggered by auto deployment on merge, or workflow_dispatch. We have always only gotten the single, following error:

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

As we are at a loss on what more we can do, we've opened a support ticket but its been multiple weeks without any real help, and minimal response. We got a response after the start of the month saying our spending limits should have reset - which is literally no help as still no Actions work. I don't think they loved into the issue at all as we had full limits well before it.

We are exploring other options for deployments CD/CI now and might as well move code storage too depending on the platform, as we can't efficiently run our business on a platform and support service like this.

[gmondello]

@justin-basd can you drop a link to your ticket and i'll take a look?

[justin-basd]

@gmondello it was raised by another user in our Organizatio. Heres the ticket

https://support.github.com/ticket/personal/0/3924302

[gmondello]

hi @justin-basd - I asked for this to be looked at by the team that can best assist you. Please continue to work with support. I'm sorry to not be able to provide more help here.

[justin-basd]

I don't think support is working with us at all since we haven't had a response for months, or any help really, but not much more we can do anyways.

My aim with raising this here is to highlight the significant issues with this Organizations may face.

[gmondello]

hi @justin-basd - I see from your other comment that you're now situated. I am sorry that it took us so long to answer your ticket.

[zeeshan965]

I am facing an issue related to github action pipeline
Ticket Link: https://support.github.com/ticket/personal/0/3996121

[justin-basd]

For our Organization the solution here was to get GitHub support to resolve whatever backend/data issue this is.

After a few months they got back to us on the ticket and fixed it within a couple hours. We were waiting from 26th of Nov 2025 for them to even look into it.

"
We're reaching back out regarding your report. We've taken a look at your organization, and the issue should be resolved. You should now be able to process using GitHubs services.
"

Unfortunately they did not provide any information on to why/what was wrong, but I assume it was out of our control either way after trying everything I mentioned in a previous comment.

My suggestion would be if you are struggling with as similar issue to raise a support ticket ASAP.

[zhewenl]

@gmondello could you help with https://support.github.com/ticket/personal/0/4039499? I've struggled days with this and would really appreciate your kind help here!!

[zylo5]

@gmondello Could you help with my ticket? I've struggled with this more than 24 hours and would really appreciate your kind help here!!

https://support.github.com/ticket/personal/0/4672123
Team Plan

[HeroSpha]

Important GitHub Billing Note
GitHub treats organizations as completely separate accounts. This means:

Payments made to your personal account do not apply to any organizations you belong to.

Each organization has its own billing settings, invoices, and payment methods.

If you want paid features (like Copilot, advanced security, or extra seats) for an organization, you must set up billing specifically for that organization.

Paying for one organization does not cover another — billing is siloed per entity.

👉 In short: personal account payments don’t cascade to organizations. You need to pay for each organization individually if you want them to have access to paid features.

[ocramz]

Thank you!

This was exactly my case: I had a personal Pro plan and own a Free org where I'm runnning lots of CI. I ran out of CI minutes on the org plan and was assuming my personal account would be billed for the overage. Activating org billing fixed this and setting the budget on CI at the org level too fixed this.

Very uninformative error message from Github tbh!

[houtanrocky]

@gmondello I'm having the same problem, and changing address didn't help, here's my ticket
https://support.github.com/ticket/personal/0/4489033

[Nathami-n]

Still have the same issue even after updating my billing information and paying up

[zylo5]

I am experiencing the same issue. There are no past dues, we have a valid payment method, and there are no issues with our spend or budget limits. We opened ticket https://support.github.com/ticket/personal/0/4672123 but have received no response yet.

We started using GitHub in April 2026 and upgraded to the Team plan in June 2026. We are planning to move all repos from our other vendor to GitHub, but this incident has left my entire engineering team sitting idle for the past 24 hours. Please investigate and resolve this immediately.

[aleks-azen]

Same on GitHub Enterprise Cloud today. Every Actions job refused at dispatch, 0 steps, for 2+ hours. Ticket: https://support.github.com/ticket/personal/0/4705945

Tried, re-testing after each: raised the Actions budget to $2,001 at 50% spend, turned off "Stop usage", replaced the card, deleted the budget entirely ("No budgets created"), created an org-scoped $5,000 budget with stop-usage off. Still blocked every time. $0 past due, no failed charges, valid card.

The billing overview kept showing "You've used 100% of the Actions budget" the whole time — including while no budget existed. Looks like stuck state on GitHub's side, not something the customer can fix.

[lucaventura]

Having this same issue. It briefly went away then came back. Been happening for the past 1.5 days....

https://support.github.com/ticket/personal/0/4712083

[Kalai141299]

We are currently using the GitHub Free/basic plan and do not want to subscribe to a paid GitHub plan.

At the end of June, our GitHub Actions usage exceeded the included free usage, and we paid approximately $4 for that month's additional usage.

After that, we returned to the basic/free plan and have not intentionally subscribed to any paid plan. However, our GitHub Actions workflows are now blocked, preventing our deployment process from running.

We tried to resolve the billing/payment issue by removing the previous payment/account information and attempting to use another GitHub account/payment method, but there is currently no payment option available for us to complete the process.

We would like to:

Continue using the GitHub Free plan.
Resolve any outstanding GitHub Actions balance, if one exists.
Understand why GitHub Actions is currently blocked.
Pay any legitimate outstanding Actions usage if required.
Have GitHub Actions restored after the billing issue is resolved.

We do not want to create a new organization because our existing repositories and deployment workflows are already configured with our current organization.

Thank you.