# 400 Error on newly created Space

**URL:** </static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2F400-error-on-newly-created-space%2F177013%3E%5C
**Category:** Spaces\
**Created:** [June 21, 2026, 5:20am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2F400-error-on-newly-created-space%2F177013 "2026-06-21T05:20:06Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![John6666](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/john6666/32/27664_2.png) [@John6666](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FJohn6666)%5C
**Post date:** [June 21, 2026, 8:00am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2F400-error-on-newly-created-space%2F177013%2F2 "2026-06-21T08:00:27Z")

</div>

Hmm… This is quite rare, but it looks similar to an error that has happened a few times before.

I can also reproduce the same public `400` as a non-owner viewer:

 ![{842BEBCE-6A4B-471E-A858-005FCBFE51AF}](https://us1.discourse-cdn.com/hellohellohello/original/3X/1/1/11ba6cdd0f6c21721173bbfcd27f161c8c88eb59.png)

```plaintext
Invalid input: expected object, received undefined -> metadata
Invalid input: expected object, received undefined -> compute
Invalid input: expected object, received undefined -> service

```

So this does not look like only a local browser/cache issue, or only an owner Settings/token issue. It looks more like the Space metadata/control-plane state is broken.

Similar reports:

- [Error 400 when creating a new space](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Ferror-400-when-creating-a-new-space%2F174705)
- [Cannot Delete Space](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fcannot-delete-space%2F174713)
- [I can’t delete or do anything to this space](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fi-cant-delete-or-do-anything-to-this-space%2F174744)

**Since you already emailed support** and also tried direct deletion, I think waiting for HF support/staff is probably the right move. I do not think there is much more to try from the user side…

---

_[View the full topic](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2F400-error-on-newly-created-space%2F177013)._