{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreian4l57homin3rm5dgoap7okytq5rxmkthxhdzhevg76uqsggp6he",
    "uri": "at://did:plc:pgryn3ephfd2xgft23qokfzt/app.bsky.feed.post/3mkqpi2nkhh72"
  },
  "path": "/t/cpu-basic-spaces-hitting-quota-limits-despite-unlimited-hosting-inconsistent-behavior-with-restart-and-factory-rebuild/175681#post_1",
  "publishedAt": "2026-04-30T21:59:08.000Z",
  "site": "https://discuss.huggingface.co",
  "textContent": "I’m encountering inconsistent and possibly contradictory behavior regarding quota limits on Docker Spaces using the free-tier **CPU-Basic** hardware.\n\n#### Summary of the issue\n\nA Space that was previously running normally entered sleep (auto-sleep). When attempting to restart it, I encountered quota-related errors that prevent it from running again.\n\n#### Observed behavior\n\n  1. After auto-sleep, clicking **“Restart Space”** results in:\n\n\n\n> “You’ve reached your null quota limit, please upgrade your account, or pause your previous Spaces to restart this one”\n>  → Redirects to a 403 page\n\n  2. As a workaround, I previously used **“Factory Rebuild”** , which successfully restarted the Space.\n  3. However, since ~2 days ago, even **Factory Rebuild** now results in:\n\n\n\n> “Space Paused — You’ve reached your hardware quota limit across all your Spaces!”\n\n  4. This occurs even when:\n\n\n  * I have very few or zero active running Spaces\n  * I tested with a completely new account (no Spaces at all), and the same error occurs\n\n\n\n#### Expected behavior\n\nAccording to the documentation, CPU-Basic Spaces are supposed to allow **unlimited hosting** (with sleep behavior). Therefore:\n\n  * Restarting a sleeping Space should not hit a quota limit if no hardware is actively in use\n  * Factory Rebuild should not immediately trigger a global hardware quota error\n  * A fresh account with zero usage should not hit any quota\n\n\n\n#### Questions\n\n  * Is there a recent change in quota policy for CPU-Basic Spaces?\n  * What does “null quota limit” refer to in this context?\n  * Are sleeping Spaces still counted toward hardware quota?\n  * Why would a fresh account hit a quota limit immediately?\n\n\n\n#### Additional notes\n\n  * This behavior started very recently (around 2 days ago)\n  * The issue affects both Restart and Factory Rebuild flows\n  * The error messages seem inconsistent (“null quota” vs “hardware quota”)\n\n\n\n* * *\n\nIf this is an intended change, clarification in the documentation would be helpful. Otherwise, this may indicate a bug in quota tracking or Space state management.",
  "title": "CPU-Basic Spaces hitting quota limits despite “unlimited hosting” — inconsistent behavior with Restart and Factory Rebuild"
}