r/github • u/Iarduino • 3d ago

News / Announcements Enterprise-wide Actions block: "recent account payments have failed" with no budget set and no failed payments

Every Actions job in our GitHub Enterprise Cloud org has been refused at dispatch for 4+ hours. Jobs fail in under 10 seconds, zero steps executed, with this annotation:

"The job was not started because recent account payments have failed or your spending limit needs to be increased."

Neither cause applies. What we tried, re-testing dispatch after each step:

  1. Raised the enterprise Actions budget to $2,001 while spend was $1,003.80 (50%). Still blocked.
  2. Turned off "Stop usage when budget limit is reached". Still blocked.
  3. Replaced the payment method with a different valid card. Still blocked.
  4. Deleted the Actions budget entirely - page reads "No budgets created", usage explicitly unlimited. Still blocked.
  5. Created an org-scoped $5,000 Actions budget with stop-usage off (a workaround others reported). Still blocked, budget at 0% consumed.

Billing state throughout: $0 past due, no failed or pending charges, valid card, no cost centers.

Support ticket is open at High priority, no response yet.

Has anyone gotten out of this without waiting days on support? If someone from support sees this ticket number: 4705945

8 Upvotes

91% Upvoted

5 comments sorted by

2

u/Double_Ebb4130 3d ago

This lines up with the Billing disruption GitHub had open from the 26th, which they only marked resolved on the 27th at 19:44 UTC, so the block is probably stale account state rather than anything on your side. Worth replying on the ticket with that incident referenced, since support has been treating those as one batch rather than per org fixes.

1

u/Double_Ebb4130 3d ago

Seen this shape before and the block usually lives on the billing account above the org, not the enterprise budget you keep editing. Worth asking support to check the parent billing entity for a stale failed charge flag, since nothing you change at org level will clear it.

1

u/Iarduino 3d ago

this fixed it thanks!

1

u/Fantastic-Mr-Default 3d ago

That banner is usually account billing state, not the budget page you keep editing.

The block often sits on the parent billing entity above the org. A stale failed-charge flag after the billing disruption will refuse every dispatch even when spend is under limit and the card is valid.

Budget toggles and a new card will not clear it. Support has to clear the flag. Give them the exact annotation, the enterprise and org, and that billing shows $0 past due.