# Spaces Build issue has been Solved
**URL:**
**Author:**  [@SiddhJagani](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FSiddhJagani)%5C
**Post date:** [November 11, 2025, 7:34am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspaces-build-issue-has-been-solved%2F170269%2F1 "2025-11-11T07:34:11Z")
---
**Author:**  [@abdelazizEl7or](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FabdelazizEl7or)%5C
**Post date:** [March 28, 2026, 5:14am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspaces-build-issue-has-been-solved%2F170269%2F2 "2026-03-28T05:14:24Z")
it’s back again 😭😭😭😭
---
**Author:**  [@Pikilap](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FPikilap)%5C
**Post date:** [March 28, 2026, 6:24am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspaces-build-issue-has-been-solved%2F170269%2F3 "2026-03-28T06:24:00Z")
I also encountered
---
**Author:**  [@John6666](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FJohn6666)%5C
**Post date:** [March 28, 2026, 7:27am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspaces-build-issue-has-been-solved%2F170269%2F4 "2026-03-28T07:27:11Z")
Maybe related:
> [@Stuck at space problem](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fstuck-at-space-problem%2F174654)%3A
>
> Previous the space what took 1min to start. Now taking 1hr in build and 1hrs in container. Idk why… I don’t get any log. I restarted, factory reset it nothing works. It’s effecting all of my spaces new and old. Is the issue my in end? When it could be fix?
---
**Author:**  [@Scrappered](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FScrappered)%5C
**Post date:** [March 28, 2026, 7:35am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspaces-build-issue-has-been-solved%2F170269%2F5 "2026-03-28T07:35:09Z")
Hi! Sorry to be asking in such a random way, (though please message me directly, I’m not good at social media’s), what’s this new limit system, and why is it extremely limiting? I only got about 2 days then the AI shut itself down for some reason, and I think it’s been over 2 weeks since I actually made a message.
---
**Author:**  [@John6666](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FJohn6666)%5C
**Post date:** [March 28, 2026, 9:07am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspaces-build-issue-has-been-solved%2F170269%2F6 "2026-03-28T09:07:44Z")
As users, we understand that this situation involves a mix of intentional changes by HF, potential bugs, and unexpected infrastructure issues.
HF is currently investigating, and not all details have been clarified yet, but broadly speaking, the following issues are intertwined. Some problems are being resolved one by one, while new ones occasionally arise…
The key point is that rather than the restrictions having become permanently stricter (at the moment), we are currently in the midst of a “mishap.”
1. Intentional (maybe) new restriction system
2. Errors (bugs?) in the restriction system
3. [Infrastructure issues (maybe related, maybe not related)](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fstuck-at-space-problem%2F174654%2F3)
---
**Author:**  [@HuyRemy](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FHuyRemy)%5C
**Post date:** [March 28, 2026, 10:30am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspaces-build-issue-has-been-solved%2F170269%2F7 "2026-03-28T10:30:41Z")
> [@John6666](#):
>
> The key point is that rather than the restrictions having become permanently stricter (at the moment), we are currently in the midst of a “mishap.”
>
> 1. Intentional (maybe) new restriction system
>
> - Automatically pauses Spaces that [violate HF policies](https://huggingface.co/content-policy)
> - [Automatically bans users](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspace-stuck-in-paused%2F169467%2F3) who create a large number of policy-violating Spaces?
>
> 1. Errors (bugs?) in the restriction system
>
> - The above measures were applied beyond HF’s intended scope
> - The resulting fallout
>
> 1. [Infrastructure issues (maybe related, maybe not related)](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fstuck-at-space-problem%2F174654%2F3)
>
> - Issues with Spaces Start, Restart, and Build
> - Strange 400 errors
> - Issues where Spaces logs are not displayed
> - and more…?
I think that is a bug, not due to policies. Maybe have some problem in HF’s base and they’re still fixing it then we should wait at least few days. It’ll be better soon.
---
**Author:**  [@John6666](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FJohn6666)%5C
**Post date:** [March 28, 2026, 11:50am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspaces-build-issue-has-been-solved%2F170269%2F8 "2026-03-28T11:50:22Z")
Yeah. Based on my interactions with support, I think it’s safe to say that this is a bug, and that the impact of the bug is the primary issue.
Well, I’m not sure if the other glitches are occurring while this bug is being fixed, or if they’re unrelated platform issues…
---
**Author:**  [@arcshukla](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Farcshukla)%5C
**Post date:** [March 28, 2026, 1:42pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspaces-build-issue-has-been-solved%2F170269%2F9 "2026-03-28T13:42:28Z")
where we can see any update from the support team on what the actual cause is and how far they have been able to fix it.. any ETA.. The status page looks all green.
---
**Author:**  [@John6666](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FJohn6666)%5C
**Post date:** [March 28, 2026, 10:13pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspaces-build-issue-has-been-solved%2F170269%2F10 "2026-03-28T22:13:08Z")
Since this issue is suspected to be caused by intentional program behavior or an error—rather than a physical infrastructure failure or an outage (at least for now)—[the status is likely to be treated as “green.”](/static-proxy?url=https%3A%2F%2Fstatus.huggingface.co%2F)
As for my correspondence with support, since it was via email, I can’t share the actual text. Sorry about that.
One thing I can say is that it seems they’ll likely post a “quick recap” of this case somewhere once the investigation is complete.
---
**Author:**  [@arcshukla](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Farcshukla)%5C
**Post date:** [March 29, 2026, 2:11am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspaces-build-issue-has-been-solved%2F170269%2F11 "2026-03-29T02:11:51Z")
Thanks for the update. Seems classic case of my systems are green, but users are still experiencing the issue. Hope to get stability and an RCA soon.
---
**Author:**  [@sukihealth](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fsukihealth)%5C
**Post date:** [April 2, 2026, 6:55am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspaces-build-issue-has-been-solved%2F170269%2F12 "2026-04-02T06:55:20Z")
How are we supposed to know what violations are done? All my spaces have been paused and I cant even do a factory rebuild, so i can’t see any logs to make appropriate changes
---
**Author:**  [@John6666](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FJohn6666)%5C
**Post date:** [April 2, 2026, 6:56am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspaces-build-issue-has-been-solved%2F170269%2F13 "2026-04-02T06:56:21Z")
As for how to check the specific reasons for violations, I only know how to do it via email… [website@huggingface.co](mailto:website@huggingface.co)