# Space forever "building" or "preparing space"

**URL:** <https://discuss.huggingface.co/t/space-forever-building-or-preparing-space/131832>\
**Category:** Spaces\
**Created:** [December 17, 2024, 6:17am UTC](https://discuss.huggingface.co/t/space-forever-building-or-preparing-space/131832 "2024-12-17T06:17:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![libra2](https://avatars.discourse-cdn.com/v4/letter/l/ce7236/32.png) [@libra2](https://discuss.huggingface.co/u/libra2)\
**Post date:** [December 17, 2024, 6:17am UTC](https://discuss.huggingface.co/t/space-forever-building-or-preparing-space/131832/1 "2024-12-17T06:17:59Z")

</div>

I have modifed the CRON\_EXPRESSION parameter in my huggingface space (i used to modify this from time to time). Then the space has been “building” and never finishes. I cannot access my space which says “preparing space”. Pls help to advise how i could fix it. Thank you.

---

<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:** [December 17, 2024, 6:38am UTC](https://discuss.huggingface.co/t/space-forever-building-or-preparing-space/131832/2 "2024-12-17T06:38:24Z")

</div>

This is a problem that has been occurring frequently recently. No workaround has been found other than to create a new space and upload the file again.

> [@Stuck in starting \[Docker Spaces\]](https://discuss.huggingface.co/t/stuck-in-starting-docker-spaces/131043):
>
> Introduction I’ve set up a custom Docker space for a Discord bot. Currently, the bot doesn’t have AI capabilities and is only sending simple messages to users in the Discord server, which works as expected. Issue However, the Docker space remains in a “starting” state, despite the bot functioning correctly. I suspect I’m missing a setting (required by hugs Spaces) that allows the Docker space to transition to a “running” state. Problem This issue is problematic because the Docker container s…
