Cannot use large host after regular host meet limitation #171251
Replies: 3 comments
-
The issue is caused by your GitHub Actions hitting the enterprise storage usage limit (50GB), which leads to hosted runners being shut down and prevents further actions until the limit is addressed. Immediate Solution Steps Create/Update Budget: Go to GitHub’s billing settings and ensure your actions/CI budget allows for overages beyond $0. This allows jobs to continue even if you exceed the free tier or current cap. Contact GitHub Support: If you’ve already set the budget and the runners still shut down, open a ticket with GitHub Support specifying your billing issue and requesting a manual reset or an increase in storage. Storage Management Details Deleting Usage May Not Help Immediately: Deleting workflow artifacts may not quickly reduce your usage if those files have already accrued storage costs over most of the billing cycle. Full Runner Removal: Removing and re-adding self-hosted or hosted runners temporarily allows for some jobs but does not reset the usage calculation for enterprise limits. Recommended Actions Monitor Storage Use: Track the total Action artifact size and storage duration via your enterprise’s Insights or billing dashboard. Communicate With Team: Let the relevant developers know about the storage policy and delete unnecessary workflow artifacts early in the billing cycle. AttemptedSolution-Effectiveness-NextSteps.csv Final Advice |
Beta Was this translation helpful? Give feedback.
-
The issue is due to GitHub Actions storage limits for enterprise accounts. GitHub-hosted runners consume storage for artifacts, logs, and caches, and when you hit the 50GB limit, jobs will fail. As an enterprise admin, you can: Check your current storage usage: Go to Settings → Enterprise → Actions → Usage to see artifact and cache storage. Increase storage: GitHub doesn’t allow manual increase beyond your plan limit; you need to upgrade your enterprise plan or purchase additional storage through GitHub sales/support. Clean up storage: Delete old artifacts and caches using the Cleanup workflow or manually via the UI. Consider reducing retention periods for Actions artifacts in your workflows. Until storage is increased, GitHub-hosted runners will hit the same limit, so cleanup + plan upgrade is required |
Beta Was this translation helpful? Give feedback.
-
I just realized I'm facing a somehow stupid condition: What we're using is why the hell are they related? why tf shutdown the large runners? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Question
Body
Hi,
all github-hosted runners are shutdown due to the enterpise action usage reached 50GB storage limitation

I created a ticket for help, the response is creating a budget can resolve

and we did the following trying:
It worked for 1 or 2 more jobs but the runner is shutdown again soon with the same error.
Any idea where I (as the enterpirise admin) can setup the extra usage of gihub storage?
The ticket has no more response for a day now, I wanna if I can find some answers here :/
Beta Was this translation helpful? Give feedback.
All reactions