GitHub Actions jobs blocked by billing message even though budget and payment method appear valid

[2yg5r4tgqt-svg]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

ARC (Actions Runner Controller)

Discussion Details

I’m experiencing an issue where GitHub Actions jobs are not starting and immediately fail with the following message:
“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.”

What I have already checked:

• The account has an active payment method.
• Recent GitHub payments show as successful.
• Billing overview does not show an outstanding payment due.
• The GitHub Actions budget has been increased and still has available headroom.
• “Stop usage when budget limit is reached” remains enabled.
• I also checked for organization-level budgets and increased the relevant Actions budget where applicable.
• Re-running the workflows after these changes produces the same billing error.
• The jobs fail before runner execution begins, so this does not appear to be a workflow-code failure.
• I have already opened a GitHub Support ticket, but I haven't received an answer yet
  Has anyone encountered a similar situation where Actions remained blocked despite having a valid payment method and sufficient Actions budget?

[kittimzhe]

Yes — this exact pattern recurs: jobs failing at creation with that message while every billing surface looks healthy. Three checks that people usually miss, all from threads where this got resolved:

1. Read the failure run's annotations, not just the job log. That message arrives as a run annotation. Two recent threads (#208350, #208368) had the same shape — runs blocked before any runner starts, all billing views green — and both resolved through billing: the askers confirmed Actions resumed the moment the payment issue cleared.

2. Check Invoices, not just payment methods. A pending invoice with a failed charge keeps the account in "no valid payment method" state even though the card on file is valid and recent payments show successful. In #208350 an invoice failure produced exactly this, with the spending-limit view looking healthy the whole time.

3. Remove and re-add the payment method. If a payment verification ever failed server-side, the account can stay flagged even after you raise budgets and confirm the card is fine. Adding a new card alongside doesn't always clear it; fully removing the failing method and adding one fresh — or setting PayPal as the default method — restarts verification on a different rail.

Beyond those: an identical case two days ago (#209042) started exactly when the budget hit 100%; raising the budget didn't lift the block, so a stale billing flag looks like the only thing that explains yours too — and that part only support can flip. In your ticket, ask specifically "is there a stuck payment verification or a failed invoice holding a billing flag on my account?" — a one-lookup question for the agent instead of a general investigation.

One nuance given the ARC tag: self-hosted runners don't consume Actions minutes, but this block gates job creation at the account level before any runner assignment — so ARC jobs fail with the same message as hosted ones.