# Spaces aren't allocating for ZeroGPU tonight
**URL:**
**Author:**  [@AbstractPhil](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FAbstractPhil)%5C
**Post date:** [August 15, 2026, 2:33am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspaces-arent-allocating-for-zerogpu-tonight%2F178683%2F1 "2026-08-15T02:33:11Z")
# Space never allocated: `hardware.current: null`, builds succeed, app never runs
Claude wrote this up to save some time. Been a bit of a journey tonight trying to get it working, so far no dice.
**Space:** `AbstractPhil/alephllm-chat` (Gradio SDK, ZeroGPU requested)
**Account:** AbstractPhil · **Observed:** 2026-08-14 → 2026-08-15
## Symptom
The Space builds successfully on every commit and is never allocated a
machine. Runtime API reports:
```auto
stage : APP_STARTING (indefinitely)
hardware : {"current": null, "requested": "zero-a10g"}
errorMessage : null
```
`current: null` persists for hours. Switching the request to `cpu-basic`
does not allocate either, so this is not ZeroGPU-specific.
## Build is not the problem
Build log completes normally every time:
```auto
--> RUN --mount=target=/tmp/requirements.txt ... CACHED
--> COPY --link --chown=1000 ./ /home/user/app DONE
--> Pushing image DONE 0.8s
--> Exporting cache DONE 0.5s
```
## The app is not the problem
The identical `app.py` runs correctly outside Spaces (same Python 3.12,
same gradio, same `spaces` package): it boots, serves `/config`, and
answers requests. It is the canonical ZeroGPU shape — model loaded at
module level and moved to `cuda`, `@spaces.GPU` on the generator, plain
`demo.launch()`. No threads, no locks, no asyncio, no coroutines, no
subprocesses of our own.
## Related history on this account (may be the same underlying issue)
1. The predecessor Space (now `AbstractPhil/alephllm-chat2`) spent ~16h
serving a **two-day-old commit** : new builds succeeded, containers
booted cleanly with `Running on local URL`, but traffic kept going to
the old revision and `runtime.sha` never advanced. Factory rebuild and
restart had no effect. Recreating the Space under a new name worked
once, then the new Space hit the `current: null` state described above.
2. `alephllm-chat2` is now **PAUSED but still reports
`hardware.current: zero-a10g`**, with `requested: cpu-basic` stuck in
flight. Re-issuing the hardware change and restarting the Space does
not apply it. It appears to be holding a hardware assignment it was
asked to release.
## Similar reports
- [Docker Space stuck in APP\_STARTING with current hardware null and 0 ready replicas](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fdocker-space-stuck-in-app-starting-with-current-hardware-null-and-0-ready-replicas%2F177813)
- [Space stuck in APP\_STARTING indefinitely](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspace-stuck-in-app-starting-indefinitely%2F177564)
## Ask
1. Why is no machine being allocated for `AbstractPhil/alephllm-chat`
despite a successful build and a pending hardware request?
2. Can the stuck hardware assignment on `AbstractPhil/alephllm-chat2`
(`current: zero-a10g` while PAUSED, `requested: cpu-basic`) be
released?
Additionally, what is this TWO LINKS PER POST thing for new users? I’m nowhere near a new user for huggingface.
---
**Author:**  [@John6666](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FJohn6666)%5C
**Post date:** [August 15, 2026, 2:52am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspaces-arent-allocating-for-zerogpu-tonight%2F178683%2F2 "2026-08-15T02:52:52Z")
Same here and there: [zero-gpu-explorers/README · All ZeroGPU Spaces stuck on "Starting" with clean logs — CPU and paid GPU unaffected](https://huggingface.co/spaces/zero-gpu-explorers/README/discussions/183#6a7fc7c8d45e5232170ab34c) @hysts
---
**Author:**  [@AbstractPhil](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FAbstractPhil)%5C
**Post date:** [August 15, 2026, 3:08am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspaces-arent-allocating-for-zerogpu-tonight%2F178683%2F3 "2026-08-15T03:08:12Z")
Well on the plus side, the AlephLLM Mini-Beatrix is perfectly playable on cpu. Pretty fun ByteLM structured system turned out pretty smart.
---
**Author:**  [@hysts](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fhysts)%5C
**Post date:** [August 15, 2026, 3:24am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspaces-arent-allocating-for-zerogpu-tonight%2F178683%2F4 "2026-08-15T03:24:20Z")
Thanks for reporting this. Looks like it’s an infra issue. I’ll check with the team internally.
---
**Author:**  [@John6666](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FJohn6666)%5C
**Post date:** [August 15, 2026, 4:17am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspaces-arent-allocating-for-zerogpu-tonight%2F178683%2F5 "2026-08-15T04:17:33Z")
Thank you!!
---
**Author:**  [@hammertoe](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fhammertoe)%5C
**Post date:** [August 15, 2026, 4:19am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspaces-arent-allocating-for-zerogpu-tonight%2F178683%2F6 "2026-08-15T04:19:17Z")
I’m also having the same issue. Just stuck in “app starting”
---
**Author:**  [@RioShiina](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FRioShiina)%5C
**Post date:** [August 15, 2026, 6:25am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspaces-arent-allocating-for-zerogpu-tonight%2F178683%2F7 "2026-08-15T06:25:44Z")
I’m experiencing the exact same issue. My ZeroGPU Space is stuck on ‘Starting’ and never transitions to ‘Running’.
---
**Author:**  [@zoeamp9](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fzoeamp9)%5C
**Post date:** [August 15, 2026, 9:06am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspaces-arent-allocating-for-zerogpu-tonight%2F178683%2F8 "2026-08-15T09:06:25Z")
> [@hysts](#):
>
> reporting
thanks 😍 for this
---
**Author:**  [@zoeamp9](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fzoeamp9)%5C
**Post date:** [August 15, 2026, 9:09am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspaces-arent-allocating-for-zerogpu-tonight%2F178683%2F9 "2026-08-15T09:09:13Z")
yes same :[zero-gpu-explorers/README · All ZeroGPU Spaces stuck on "Starting" with clean logs — CPU and paid GPU unaffected](https://huggingface.co/spaces/zero-gpu-explorers/README/discussions/183#6a7fc7c8d45e5232170ab34c)
---
**Author:**  [@hysts](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fhysts)%5C
**Post date:** [August 15, 2026, 1:15pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspaces-arent-allocating-for-zerogpu-tonight%2F178683%2F10 "2026-08-15T13:15:44Z")
Should be resolved now. Thanks!
---
**Author:**  [@John6666](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FJohn6666)%5C
**Post date:** [August 15, 2026, 8:19pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspaces-arent-allocating-for-zerogpu-tonight%2F178683%2F12 "2026-08-15T20:19:01Z")
I confirmed! Thanks a lot!
---
**Author:**  [@system](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fsystem)%5C
**Post date:** [August 16, 2026, 8:19am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspaces-arent-allocating-for-zerogpu-tonight%2F178683%2F13 "2026-08-16T08:19:26Z")
Closed on August 16, 2026, 8:19am UTC
This topic was automatically closed 12 hours after the last reply. New replies are no longer allowed.