GitHub Actions disabled after heavy CI/CD usage has anyone experienced this?

[Frost-bit-star]

Why are you starting this discussion?

Question

What GitHub Actions topic or product is this about?

General

Discussion Details

I’m opening this to understand if others have run into a similar situation.

After a period of heavy CI/CD usage (frequent workflow runs, testing, automation across repos), my GitHub Actions were disabled at the account level. I didn’t change any repo settings myself, and the workflows were for legitimate open source CI tasks.

Since then, my GitHub Sponsors profile has also been stuck in “pending review” for months, which makes me think this is related to account trust or automated abuse prevention.

I’m curious:

Has anyone had Actions disabled after high CI usage?

What triggered it in your case?

How long did it take to get resolved after contacting GitHub Support?

Was there anything specific you had to clarify or change?

Sharing experiences would really help, especially for maintainers running automation-heavy open source projects.

[herwingx]

1. Usage Limits (Monthly Quotas)
For public repositories, GitHub Actions is free and unlimited in terms of minutes and storage. For private repositories, the monthly limits are:

GitHub Free: 2,000 minutes and 500 MB of storage.

GitHub Pro: 3,000 minutes and 2 GB of storage.

GitHub Team: 10,000 minutes and 5 GB of storage.

GitHub Enterprise Cloud: 50,000 minutes and 50 GB of storage.

2. Execution and Concurrency Limits
Even if you have minutes available, there are technical capacity constraints:

Concurrent Jobs: The Free plan allows up to 20 concurrent jobs; Pro allows 40, and Team 60. Any excess jobs will be placed in a queued state.

Maximum Execution Time: A single job can run for a maximum of 6 hours on GitHub-hosted runners (5 days for self-hosted) before being automatically cancelled.

Job Matrix: A workflow cannot generate more than 256 jobs per execution.

Cache: There is a limit of 10 GB per repository and, as of January 2026, a limit of 200 cache uploads per minute.

3. What Happens if You Exceed the Limits?
Additional Charges: If you have a spending limit configured, GitHub will bill you for every extra minute or GB once your free quota is exhausted.

Execution Block: If your spending limit is set to $0, Actions in private repositories will stop running until the next billing cycle.

2026 Update: Starting March 1, 2026, using self-hosted runners in private or enterprise repositories will incur a cost of $0.002 per minute.

4. Why are my Actions "Pending Review" or "Paused"?
If your actions aren't progressing, it’s usually due to:

Awaiting Approval (Review): For security, if an external contributor submits a Pull Request from a fork, an admin must manually approve the Action execution.

Concurrency Queue: You’ve hit the simultaneous job limit for your plan.

Dependencies: The job is configured with the needs: keyword and is waiting for a previous job to complete successfully.

Runner Unavailability: If you use self-hosted runners, the server might be offline or overloaded.

Branch Protection Rules: If the branch has rules requiring status checks, the job may appear as "waiting" until specific conditions are met.

[Frost-bit-star]

It's been months....it stops working last year feb

[Gecko51]

This sounds like your account got flagged by GitHub's automated abuse detection system. It happens sometimes with heavy CI usage, especially if the pattern looks unusual to their heuristics (lots of concurrent runs, frequent triggers, automation across many repos at once).

The bad news: once your account is flagged at this level, there's no self-service fix. The comment above about usage limits is accurate for normal scenarios, but your situation is different. Account-level disabling and the Sponsors profile being stuck in review are both signs of a trust/compliance hold on your account.

Here's what I'd do:

1. Open a support ticket at https://support.github.com, specifically under the Actions category. Be clear that Actions were disabled at the account level, not just a single repo.

2. In the ticket, explain your use case: open source CI, the types of workflows you run, and that you weren't doing anything shady. If you can share example repos and workflow files, do it. The more context they have, the faster they can clear you.

3. Mention the Sponsors issue too, since it's almost certainly the same internal flag blocking both.

4. If you don't hear back within a week, reply to the ticket. Support queues can be slow but replies tend to bump priority.

One thing to keep in mind for the future: if you're running heavy automation, consider self-hosted runners for the burst workloads. It avoids tripping the abuse detection on GitHub-hosted runners entirely.

How long ago did you contact support?