GitHub Actions jobs blocked by billing-related account restriction

[JohnkayFundz]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

Other

Discussion Details

Hello GitHub Community,

I'm trying to validate a pull request in my repository, but neither GitHub Actions job starts. Both jobs display this error:

“The job was not started because your account is locked due to a billing issue.”

My GitHub billing overview currently shows:

• GitHub Free: $0/month
• Current metered usage: $0
• No next payment due displayed

The workflow jobs fail almost immediately without starting, and no runner is assigned. This appears to be an account or billing restriction rather than a code-test failure.

Could someone advise me on how to identify the cause and restore GitHub Actions access without incurring unnecessary charges?

Repository: https://github.com/JohnkayFundz/techstore-pro

Failed workflow: https://github.com/JohnkayFundz/techstore-pro/actions/runs/38137492647

Thank you.

[JohnkayFundz]

Update: Further investigation of the account restriction

I checked my GitHub Billing & Licensing page and found this message:

“This account is disabled because we have not been able to charge it for another month.”

My account currently shows GitHub Free and Copilot Free, with $0 in current metered usage.

I also tried contacting GitHub Support through the General Billing and Payments form. After completing the form, I was redirected to an automatically generated solution page instead of receiving confirmation that a support ticket had been created.

My GitHub Actions jobs remain blocked by the billing-related account restriction.

Could someone advise how I can get this restriction investigated, confirm whether an outstanding balance exists and which product it relates to, and determine whether my account can be restored without activating a paid subscription or triggering an unexpected charge?

Repository: https://github.com/JohnkayFundz/techstore-pro

Failed workflow: https://github.com/JohnkayFundz/techstore-pro/actions/runs/38137492647

Thank you.

[aviralpls]

Hey! That second message is the useful clue. “We have not been able to charge it for another month” means GitHub tried to bill something on your account and the charge failed, even though the plan shows Free and $0 usage. The Actions error is just a side effect of that lock. Here’s how I’d track it down:

1. Find what’s actually being billed

Go through these in Settings, since the billing overview can look clean while something else is failing:

Billing and licensing → Billing history / Payment information. Look for a failed or past-due charge, or a payment method that’s expired or removed.
Billing and licensing → Subscriptions (or Licensing). Check for a Copilot Pro/Pro+ trial that converted, a Marketplace app, or GitHub Sponsors. A trial that quietly turned into a paid plan and then failed to charge is a very common cause.
Settings → Applications → Marketplace/Installed apps. Look for any paid app tied to your account.
Your spending/budget settings. A $0 budget with stop-usage enabled can also block jobs, though that usually shows a different message.

2. Fix it without paying for anything new

If you find a paid subscription you don’t want, cancel it. Once it’s cancelled and there’s no outstanding balance, the lock should clear.
If there’s a real failed charge, updating the payment method and letting it retry is usually the fastest route. A bill that already exists has to be settled either way, and cancelling afterwards stops it from recurring.
Check the email tied to your account, including spam, for any billing notices from GitHub. They usually name the product and the amount.

3. Getting a human at support

The auto-generated solution page after the billing form is a deflection step. Look at the bottom of it for an option like “Contact Support” or “I still need help”, or go straight to support.github.com/contact and pick the billing category again while logged in. Include the exact message from your billing page and the failed run URL, since that tells them it’s a billing lock and not a workflow bug. Billing tickets aren’t routed through the community, so this is the only route that can actually clear the flag.

4. In the meantime

You can still validate the PR locally by running the tests or linters on your machine. Whether public repos are affected depends on what’s locked, so I wouldn’t assume that as a workaround.

Once the lock is cleared, just re-run the failed jobs from the Actions tab. Hope you get it sorted. If you find out what the culprit was, post it here so it helps the next person.

[Yoosuf01]

Hi @JohnkayFundz
This error typically triggers when an automated recurring charge fails, which forces GitHub to place a hard lock on compute resources like GitHub Actions across all repositories, even free ones.
Since your main dashboard shows $0, the hidden charge is almost always a grandfathered Marketplace extension, an ended Copilot trial, or an organization-level billing mismatch.
Here is exactly how to uncover the hidden charge, along with a custom local validation workaround so you can keep testing your MERN stack while GitHub Support clears the flag:

1. Audit Hidden Billing Items

Navigate explicitly to these deep settings URLs to uncover hidden dues:
• Check GitHub Marketplace Subscriptions: Go to Settings -> Applications -> Installed GitHub Apps and check the Marketplace tab. Look for third-party linters, CI add-ons, or agile boards that might have quietly rolled into a paid tier.
• Inspect the Payment History Logs: Do not rely on the summary card. Go directly to Settings -> Billing and licensing -> Payment information and scroll down to your Billing History. Look for any line items marked Failed or Pending.
• Verify Organization Isolation: If techstore-pro was ever transferred to or from a GitHub Organization structure, check the organization's independent billing settings panel, as organization balances do not sync to personal dashboards.

2. Bypass the Support Deflection Screen

The automatic guide page you hit is an AI firewall. To bypass it and route your ticket directly to a human specialist:

1. Go directly to support.github.com/contact.

2. Select Billing and Payments as the primary category.

3. On the solution preview window, scroll to the absolute bottom and click "I still need help" or "Open a Ticket".

4. Attach your specific run error: The job was not started because your account is locked due to a billing issue. This will instantly route the ticket out of the standard technical queue and directly to the accounts team who have database permission flags to lift the restriction.

5. How to Validate Your Pull Requests Locally (Workaround)

Since your workflow runs standard frontend lint/build processes and backend validations, you don’t have to wait for the GitHub cloud runners to fix themselves.
You can execute a complete local validation sweep using your terminal. From the root directory of your cloned techstore-pro project, run this composite validation sequence to mimic your Actions workflow:
bash

Validate frontend architecture

cd client && npm install && npm run lint && npm run build

Validate backend systems

cd ../server && npm install && npm test
Use code with caution.
If this passes cleanly on your machine, your code is solid, and you can confidently merge the pull request once your billing access is restored by support!

[Yoosuf01]

Here is a pre-formatted template you can submit directly to the billing team. It includes all the right keywords to bypass the automated triage bot and get assigned to a human technician who can clear account flags:

Support Ticket Template

Subject:
Urgent: Account Locked Due to Billing Issue Affecting GitHub Actions (Free Tier MERN Project)
Category:
Billing and Payments -> Account Restrictions
Ticket Body:
text
Hello GitHub Support Team,

I am writing to request an urgent investigation into a billing restriction that has locked GitHub Actions functionality on my free-tier account.

My repository workflows are failing immediately with the following error:
“The job was not started because your account is locked due to a billing issue.”

Failed Run URL: https://github.com/JohnkayFundz/techstore-pro/actions/runs/38137492647

Context & Troubleshooting Steps Taken:

1. My Billing & Licensing page currently shows the message: “This account is disabled because we have not been able to charge it for another month.”
2. However, my primary billing dashboard shows that I am on the GitHub Free plan, with $0 in current metered usage, and no outstanding balance or upcoming payments listed.
3. I am not currently utilizing any active paid extensions, Marketplace apps, or paid Copilot plans.

Could a billing specialist please audit my account to check for any hidden, failed, or pending transactions that are triggering this lock? If there is an outstanding balance from a trial or secondary service, please advise on how I can settle it or clear the restriction so I can resume running CI/CD validation on my public open-source projects.

Thank you for your assistance.

Best regards,
[Your Username]