Artifact Storage Quota Limit Reached - Deployment Blocked

[tasosger]

Why are you starting this discussion?

Question

What GitHub Actions topic or product is this about?

Misc

Discussion Details

Artifact Storage Quota Limit Reached - Deployment Blocked

Hi everyone,

I am currently running into an issue with GitHub Actions where the artifact storage quota has been exceeded, which is blocking my deployments.

The error message we’re seeing:

Error: Failed to CreateArtifact: Artifact storage quota has been hit. Unable to upload any new artifacts. Usage is recalculated every 6-12 hours.

I deleted all artifacts and waited for more than 12 hours but i am still getting the same message.
Does anyone know how to solve this?

Thanks!

[sprinter-cjenkins]

I'm encountering the same issue with artifact quota limits. I tried address it by cleared all existing artifacts and removed older deployments to free up space but this did not work... the problem started on June 5 or 6 2025.

[Arunabh-Sen]

Delete old artifacts and wait up to 24 hours. if the issue persists, contact GitHub support or upgrade your plan.

[mscbuild]

The "Artifact Storage Quota Limit Reached" error means you've exceeded the storage capacity allocated for artifacts in your repository. To fix this, you need to either delete old artifacts to free up space, or potentially increase your storage quota or upgrade your plan if you have a subscription.
*Check your quota:
Determine how much storage you have available and how much is being used. This information is usually found in your repository or account settings, or within the billing section of your cloud provider (e.g., GitHub ).
*Examine recent deployments:
See if any recent builds or deployments have resulted in a large number of artifacts, possibly contributing to the quota limit.
Resolve the Issue:
*Delete old artifacts:
The most common solution is to delete artifacts you no longer need. You can find and delete artifacts through your repository or account settings.
*By following these steps, you can resolve the "Artifact Storage Quota Limit Reached" error and prevent future deployments from being blocked.
*Open a new one.....

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[garcipat]

I have the same issue. Deleted runs and artifacts but the issue persists.

[keith-navys-ai]

I have the same issue. Have cleared cache and artifacts, but the builds still fail.

[slovacek-edhouse]

There is definitely something wrong with GitHub in this regards. I see a huge disconnect between what is declared by GH (Usage is recalculated every 6-12 hours.) and what is actually perceived by us users.

And yes, I am one of those who hit the quota limit, deleted many workflow runs, set retention period to 1 day, waited well over 24 hours and still is facing the issue.

Support ticket filed.

[cosmolev]

Was the issue resolved after you filed the support ticket?

[slovacek-edhouse]

No, the support ticket only helped me to understand how the quota works. I have summarized it on StackOverflow: https://stackoverflow.com/questions/70730786/github-actions-create-artifact-container-failed-artifact-storage-quota-has-b/79801579#79801579

[keith-navys-ai]

I had to set a budget (I used .50 cents), and it resolved immediately. The response I got was that the storage limits don’t reset immediately, or even in 6-12 hours - they reset the next billing cycle. The only workaround I found was to set a budget. Get Outlook for iOS<https://aka.ms/o0ukef> Keith Hickman Co-Founder & CTO E ***@***.*** W navys.ai This email and any attachments are confidential and intended solely for the use of the individual or entity to whom they are addressed. Unauthorised use, disclosure or copying of this communication or any part thereof is strictly prohibited and may be unlawful. If you have received this communication in error, please notify the sender immediately by return e-mail or by e-mail to ***@***.***, and delete this communication and all copies thereof, including all attachments.

…

________________________________ From: Lev ***@***.***> Sent: Wednesday, October 29, 2025 9:20:16 AM To: community/community ***@***.***> Cc: Keith Hickman ***@***.***>; Comment ***@***.***> Subject: Re: [community/community] Artifact Storage Quota Limit Reached - Deployment Blocked (Discussion #162223) Was the issue resolved after you filed the support ticket? — Reply to this email directly, view it on GitHub<#162223 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BR4D5KTV5JK4KUU5WHK6OHL32B2EBAVCNFSM6AAAAAB64K6M3CVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIOBRGI4TSNI>. You are receiving this because you commented.Message ID: ***@***.***>

[slovacek-edhouse]

No, it's not the caches, it's not that backend has not yet recalculated something.

The issue is (and also a common misunderstanding) that storage quota includes time factor - it is billed based on hourly usage of artifacts throughout the month. Once you hit the quota, you cannot "undo" it by deleting your artifacts (and possibly caches). You can only 1) wait till the end of month, 2) add a budget to storage, 3) mark your repository as public. See my full answer on SO

[quantuminformation]

2 days of -> Failed to CreateArtifact: Artifact storage quota has been hit. Unable to upload any new artifacts. Usage is recalculated every 6-12 hours.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[yasslbk]

This error is confusing, but the key point is:
GitHub Actions storage is not just “how much you have now”, it’s “how much you used over time” (GB-hours).

---

Why deleting artifacts doesn’t fix it

Even though the docs say:

“Deleting artifacts frees up space for current storage…does not reduce your accrued storage usage for the current billing cycle.”
https://docs.github.com/en/billing/concepts/product-billing/github-actions#calculating-minute-and-storage-spending

That “accrued usage” is what actually matters here.

So if you already hit the monthly quota, deleting artifacts:

• frees disk space
• but does NOT undo what you already used this month

---

What this means in practice

• Once you hit the limit → uploads are blocked
• Cleanup won’t unblock you for the current billing cycle
• The 6–12h delay only updates the numbers, it doesn’t reset usage

---

How to fix it

Only 3 real options:

• increase your Actions spending limit (fastest fix)
• make the repo public (if possible)
• wait for the next billing cycle

---

TL;DR

• quota = size × time (GB-hours)
• you already used all your quota
• need to wait until next month or increase quota

---