All hosted Actions jobs refused after org moved into an Enterprise: "recent account payments have failed" with $0 past due, budgets under limit

[ClownWorld-LoL]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

Other

Discussion Details

Our org started as a standard org on its own billing. We created an Enterprise account and moved the org into it, so billing moved to the enterprise level and the org no longer has its own payment method.

Since about 15:50 UTC Oct 5, our larger runners show "Shutdown: Runners are shut down due to spending limit caps being reached". Since about 05:00 UTC Oct 6, every GitHub-hosted job is refused within seconds with: "The job was not started because recent account payments have failed or your spending limit needs to be increased."

What we have checked:

• The enterprise shows $0 past due, the last payment succeeded and a valid card is on file.
• The enterprise Actions budget is $20,000 and about $1,000 is used.
• The org-level budgets cannot be edited or deleted ("a valid payment method is required"), and there is nowhere to add a payment method at the org level.
• Re-running a job after confirming all of this is still refused in 4 seconds.

This looks like the same pattern as #130816 (org upgraded to Enterprise, billing and Actions broke) and #167073 (enterprise Actions blocked with budgets under limit, later lifted by GitHub support), and similar to #199036.

Has anyone had this resolved faster than waiting on a ticket, or found which setting or flag was responsible? We have a support ticket open and have asked for escalation to a billing engineer.