Enterprise Actions blocked despite budget headroom — support case #4732160

[mathewsf3]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

Other

Discussion Details

Our FluxoKit GitHub Enterprise Cloud account is encountering an Actions billing restriction. Required checks on our private repository fail before any steps execute, preventing our normal validated merges and releases.

Existing support case: #4732160. We have provided the affected run and detailed billing evidence privately in that case.

The job annotation 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

What we verified on September 5, 2026:

• The enterprise billing overview shows $0 past due.
• Actions net metered usage is approximately $1,000.60, against a $2,000 enterprise-managed Actions budget with Stop usage enabled.
• The older $500 organization Actions budget is alerts-only, with Stop usage disabled.
• The 50,000 included Actions minutes have been consumed.
• An unexpired payment method is saved. No failed payment or Pay now/retry-payment action is visible in the billing UI. We cannot confirm whether a separate authorization has failed.
• The affected GitHub-hosted job has zero executed steps; this is a rejection before execution rather than a test failure.

We searched and found related reports in #199036 and #151956, but we do not know whether the underlying cause is the same.

Has another Enterprise Cloud organization resolved this combination of symptoms, and what specific supported action restored Actions?

If GitHub staff can help route existing case #4732160 to the appropriate billing/account-review team, we would appreciate it. We need the team to identify any failed authorization, account-level usage restriction, or enterprise/organization billing association problem. If payment is required, please provide the exact amount and action through the private support case. We want to retain our $2,000 hard cap.

We understand that the community cannot inspect private billing state. We are looking for confirmed recovery experience and the correct support route; the account-level cause is still unconfirmed.