App stuck on 'Solving environment' for 2+ hours — Conda solver deadlocked, please clear environment cache

My app web-scraping-and-data-collection.streamlit.app has been stuck on ‘Solving environment’ for over 2 hours. The Conda solver is deadlocked. I have removed all extra packages from environment.yml and deleted/redeployed the app, but the solver is still frozen at the same timestamp (18:11:10 ). Please clear the environment cache for this app.

Hey there, thanks for reaching out and sorry you’re running into this! :rocket: When a Streamlit Community Cloud app is stuck on “Solving environment” for hours, it’s almost always due to the conda environment resolution process hitting resource (memory) limits or getting deadlocked—unfortunately, there is no way for users or moderators to manually clear or reset the environment cache for a specific app.

Streamlit Community Cloud will always use the first dependency file it finds (environment.yml, requirements.txt, etc.), and if environment.yml is present, it will use conda to resolve dependencies. This process is known to be slow and memory-intensive, especially with conda-forge or many dependencies, and can fail silently or hang indefinitely if the environment is too complex or the server runs out of memory. The official recommendation is to use a minimal requirements.txt file instead of environment.yml whenever possible, as pip-based installs are much faster and more reliable on Community Cloud. If you must use conda, try to further simplify your environment.yml, avoid unnecessary channels, and remove any non-essential packages. If the problem persists, consider switching to requirements.txt or deploying on a platform with more resources. For more details, see the official docs and related forum threads: resource limits, app dependencies.

Sources: