{"slug": "space-stuck-restarting-on-an-old-commit-for-16-hours-new-builds-succeed-but-get", "title": "Space stuck \"Restarting\" on an old commit for 16+ hours — new builds succeed but never get traffic", "summary": "A Hugging Face Space by user anandkr has been stuck in a 'Restarting' state for over 16 hours, failing to serve traffic from new builds despite successful container startups. The issue persists across multiple commits and is not resolved by factory rebuild or restart actions, indicating a platform-side deployment problem.", "body_md": "Space: [Ama Backend - a Hugging Face Space by anandkr](https://huggingface.co/spaces/anandkr/ama-backend)\n\nHardware: CPU basic (free tier, 2 vCPU / 16GB RAM)\n\nMy Space has been stuck showing “Restarting” for over 16 hours. The UI tooltip says *“This Space is restarting on commit 8240352. You can still use the previous version while it restarts.”* — but `8240352`\n\nis a commit from several hours **before** my most recent pushes, and the Space has never progressed past this message despite multiple newer commits building successfully.\n\n**Timeline / what I’ve tried:**\n\n`17f9b0b`\n\n(code change to `server.py`\n\n, `requirements.txt`\n\n, `.dockerignore`\n\n). Build succeeded. Container logs showed a clean startup: `Application Startup`\n\n→ model loading → `Application startup complete`\n\n→ `Uvicorn running on `` http://0.0.0.0:7860`\n\n. Dashboard still showed “Restarting.”`ba4dd3b`\n\n(fixed a `numpy`\n\nversion issue from the previous build). Build log shows a fully successful `pip install`\n\nand image push, no errors. Container logs again show a clean, healthy startup ending in `Background load: resources ready.`\n\n. Dashboard still showed “Restarting,” with the same tooltip referencing the old `8240352`\n\ncommit.`c583b52`\n\n(prompt change only). Same result: build succeeds cleanly (full log available if useful), but the Space dashboard stays on “Restarting,” and the live endpoint (`https://anandkr-ama-backend.hf.space`\n\n) keeps serving responses consistent with the old, pre-`17f9b0b`\n\ncode (verified by testing endpoint behavior that only exists in the new code, e.g. a `503 \"warming up\"`\n\nresponse right after restart vs. the old blocking behavior, and a prompt-wording change that’s absent from live responses).**Summary:** Every new build of this Space (3 in a row) completes successfully and the container itself starts up healthy per its own logs, but the Space never transitions to “Running” and traffic never cuts over to the new container. The two dedicated recovery actions (Factory rebuild, Restart this Space) had no observable effect either — Factory rebuild didn’t even appear to start a new build.\n\nDev Mode has never been enabled on this Space, so that’s ruled out as a cause (a common root cause for similar “stuck on old commit” reports on this forum).\n\nThis looks like a stuck deployment/cutover state on the platform side rather than anything in my Dockerfile or app code, since the same Dockerfile/app builds and boots cleanly every time. Has anyone seen this before, or is there a way to force a clean redeploy / get this Space un-stuck?", "url": "https://wpnews.pro/news/space-stuck-restarting-on-an-old-commit-for-16-hours-new-builds-succeed-but-get", "canonical_source": "https://discuss.huggingface.co/t/space-stuck-restarting-on-an-old-commit-for-16-hours-new-builds-succeed-but-never-get-traffic/177049#post_1", "published_at": "2026-06-22 00:10:48+00:00", "updated_at": "2026-06-22 00:30:41.615153+00:00", "lang": "en", "topics": ["ai-infrastructure", "developer-tools"], "entities": ["Hugging Face", "anandkr", "Ama Backend"], "alternates": {"html": "https://wpnews.pro/news/space-stuck-restarting-on-an-old-commit-for-16-hours-new-builds-succeed-but-get", "markdown": "https://wpnews.pro/news/space-stuck-restarting-on-an-old-commit-for-16-hours-new-builds-succeed-but-get.md", "text": "https://wpnews.pro/news/space-stuck-restarting-on-an-old-commit-for-16-hours-new-builds-succeed-but-get.txt", "jsonld": "https://wpnews.pro/news/space-stuck-restarting-on-an-old-commit-for-16-hours-new-builds-succeed-but-get.jsonld"}}