{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihgqnnncc7si77ilcdq25rh45m3j44bakw7252donv36xaxo2a44a",
    "uri": "at://did:plc:pgryn3ephfd2xgft23qokfzt/app.bsky.feed.post/3mphfik4xjvo2"
  },
  "path": "/t/cannot-restart-my-private-space-503-something-went-wrong-when-restarting-this-space/177235#post_3",
  "publishedAt": "2026-06-29T20:23:27.000Z",
  "site": "https://discuss.huggingface.co",
  "textContent": "I think there is enough information in my post. The “**503.** Something went wrong when restarting this Space.” is a known HF-issued error that is user-unfixable. This is why I included the “**Request ID** : Root=1-6a42562f-1dfaffa84dbd985f5b11284a”\n\n> **Restart / Factory rebuild fails, but no new Build or Container logs appear at all.**\n>  In that case, I would stop treating it as only an application-code problem. It may be stuck before your app code is even reached: Space lifecycle state, scheduling/build dispatch, stale runtime state, or a policy/lock state that only HF staff can inspect.\n\nThis is my case.\nThere are no build logs. The builds are not even triggered. The Space looks completely disabled.\n\n> HF-side inspection may be needed.\n\nThis is why I’ve created this thread to get help from the HF staff.",
  "title": "Cannot restart my private space: \"503. Something went wrong when restarting this Space.\""
}