# Flowise Space Stuck on Building

**URL:** <https://discuss.huggingface.co/t/flowise-space-stuck-on-building/103813>\
**Category:** Spaces\
**Created:** [August 24, 2024, 2:44pm UTC](https://discuss.huggingface.co/t/flowise-space-stuck-on-building/103813 "2024-08-24T14:44:13Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![John6666](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/john6666/32/27664_2.png) [@John6666](https://discuss.huggingface.co/u/John6666)\
**Post date:** [August 24, 2024, 3:44pm UTC](https://discuss.huggingface.co/t/flowise-space-stuck-on-building/103813/4 "2024-08-24T15:44:33Z")

</div>

> [@Space is Building... permanently](https://discuss.huggingface.co/t/space-is-building-permanently/99740/14):
>
> This is not a Gradio-only problem. I am using a Docker space. @radames any ideas?

It was two weeks ago.  
Somehow, I don’t think there is more than one cause of the build error, but at least at my time, it seemed that something higher up in the virtual machine, not Gradio, was scanning all the components of the demo just before launching the demo, executing the main functions and trying to get a sample output It seemed to be.  
If there is a way to make it impossible to get samples, it might solve the problem in a non-Gradio environment if the cause is the same as mine.

If you are in a hurry, it may be faster to contact HF staff on Discord.😞  
Or there, since they are just now soliciting feedback on the Post.

> **[@victor on Hugging Face: "🙋 Calling all Hugging Face users! We want to hear...](https://huggingface.co/posts/victor/964839563451127)**
>
> We’re on a journey to advance and democratize artificial intelligence through open source and open science.

---

_[View the full topic](https://discuss.huggingface.co/t/flowise-space-stuck-on-building/103813)._
