# Gradio Spaces stuck in NO_APP_FILE despite valid app.py and README.md

> Source: <https://discuss.huggingface.co/t/gradio-spaces-stuck-in-no-app-file-despite-valid-app-py-and-readme-md/192099#post_3>
> Published: 2026-11-20 03:05:13+00:00

**Recommendation:** When a Gradio Space won't start, duplicate gradio/hello_world with sdk_version 5.49.1 on CPU Basic to rule out a platform-side failure before changing your repo, and verify app_file matches an existing file such as run.py.
More in the playbook "Running AI in production": <https://wpnews.pro/playbooks/production-ops>

Adding to the above: I’ve built Spaces thousands of times. Most “won’t start” problems are config mistakes, but in my experience roughly 10% are silent failures on the HF side, such as a network or repository error. When that happens, nothing you change in your repo helps, and you just have to wait.

The tricky part is that these platform-side failures look exactly like config errors from the outside. So my approach is to try one quick fix, and if that doesn’t work, rule out the platform first instead of tweaking your repo over and over.

The fastest way to rule it out is to duplicate the official [gradio/hello_world](https://huggingface.co/spaces/gradio/hello_world) Space, change `sdk_version` to `5.49.1`, and keep the same hardware (CPU Basic). I just did this myself and it runs fine on 5.49.1: [Renecto/hello_world](https://huggingface.co/spaces/Renecto/hello_world). One thing I hadn’t noticed before: the official template’s README uses `app_file: run.py`, not `app.py`, so make sure `app_file` points to a file that actually exists.

Your Space is private, so I can’t see it. That’s about as far as I can help from here.
