Rebooting the app is not working

Using Streamlit
1

When I push changes via Github, I have to reboot the app every time to make these changes visible.
Since this morning, the app has been rebooting in an endless loop.
Unfortunately, I have noticed for some time that the use of Streamlit is getting worse and worse.

1 Like
2

I am experiencing the same issue, my app was working yesterday perfectly fine but today when I went to the deployed link it is not working anymore and it is keep loading the app even after the reboot with the “Your App is in the oven” screen.
Please fix it or let us know what’s the issue. I thought the cloud is down but other community apps are just working fine.

2 Likes
4

Yes, here too. Another one works perfectly, the other one is in the oven and won’t come out.

5

Same for me too. I even tested rebooting an app that I made no changes to and it suffered the same fate. Stuck in the oven, forever provisioning the machine. Hopefully it’s resolved soon.

2 Likes
6

An issue was recently identified and fixed. Are you still having an issue?

1 Like
7

Thx. It’s working so far.

8

@mathcatsand It seems that the problem is recurring.

9

Can you share a link to your app and repo?

10

I’m beyond frustrated with this ongoing issue. My app was running smoothly until recently, but now it’s stuck in the endless “Your App is in the oven” loop. Even after multiple reboots, there’s no improvement, and it’s starting to seriously impact my work. It’s becoming increasingly difficult to rely on Streamlit Cloud when basic functionality like this is unreliable. If this problem isn’t resolved soon, it might be time to look into alternatives. We need transparency on what’s happening and an immediate fix. Streamlit Cloud should be able to handle such simple deployments without all this hassle.

11

Please can you share a link to your app so I can forward it for investigation? There appears to be a recurrence of the issue, but I need specific apps to forward to engineering. Thanks.

12

I am experiencing this issue today with a private app. I see that the app has gone down and can click the reboot button but it is not doing anything. Immediately after clicking reboot, the app shows that it is down and has no period where it is “in the oven.” Up until 15 minutes ago the app was running normally and has no code changes in >3 months. Currently running streamlit==1.27.2

13

Update - upgrading and downgrading streamlit version fixed the issue

1 Like
14

what do you mean? are you talking about the local environment (pyenv or conda)?

16

@Roger2 Your app appears to be deployed now. You’re just missing your environment configuration:

17

Non, the app is not deployed. Not properly at least. All we get is a ‘Module not found error’, this was working great a last week. Now the same repo is not working.

It still works on my computer locally with streamlit, but not on the cloud.

What do you mean ‘environment configuration’? The environment.yml file is in the repo. Where does this happen at?

I have simplified the environment.yml file by doing: conda env export --from-history > environment.yml. This usually works with cross platform problems. here is the environment.yml file:

name: demoassistant
channels:

  • conda-forge
  • defaults
    dependencies:
  • python=3.10
  • numpy
  • pandas
  • pydantic
  • scikit-learn
  • langchain
  • langchain-core
  • langchain-openai
  • plotly
  • streamlit
  • python-dotenv
  • tabulate

endfile

Thanks

Roger Erismann

18

Now the app just goes to an error their is nothing in the logs, here is the log :

[ UTC ] Logs for reporterdemo-hammerdirt.streamlit.app/
────────────────────────────────────────────────────────────────────────────────────────
[07:25:08] :desktop_computer: Provisioning machine…
[07:25:08] :control_knobs: Preparing system…
[07:25:08] :chains: Spinning up manager process…
[06:38:51] :rocket: Starting up repository: ‘reporter_demo’, branch: ‘main’, main module: ‘app.py’
[06:38:51] :octopus: Cloning repository…
[06:38:54] :octopus: Cloning into ‘/mount/src/reporter_demo’…

[06:38:54] :octopus: Cloned repository!
[06:38:54] :octopus: Pulling code changes from Github…
[06:38:56] :package: Processing dependencies…
Retrieving notices: [2025-01-23 06:38:56.992914] /home/adminuser/.conda/lib/python3.10/site-packages/conda/base/context.py:201: FutureWarning: Adding ‘defaults’ to channel list implicitly is deprecated and will be removed in 25.3.

To remove this warning, please choose a default channel explicitly with conda’s regular configuration system, e.g. by adding ‘defaults’ to the list of channels:

conda config --add channels defaults

For more information see Using the .condarc conda configuration file — conda 25.1.0 documentation

deprecated.topic(

  • [2025-01-23 06:38:57.092565] \ [2025-01-23 06:38:57.194537] | [2025-01-23 06:38:57.299554] / [2025-01-23 06:38:57.409601] done
    /home/adminuser/.conda/lib/python3.10/site-packages/conda/base/context.py:201: FutureWarning: Adding ‘defaults’ to channel list implicitly is deprecated and will be removed in 25.3.

To remove this warning, please choose a default channel explicitly with conda’s regular configuration system, e.g. by adding ‘defaults’ to the list of channels:

conda config --add channels defaults

For more information see Using the .condarc conda configuration file — conda 25.1.0 documentation

deprecated.topic(
Channels:

  • conda-forge
  • defaults
    Platform: linux-64
    Collecting package metadata (repodata.json): …working… [2025-01-23 06:39:14.492410] done
    Solving environment: …working…
    [07:34:47] :snake: Python dependencies were installed from /mount/src/reporter_demo/environment.yml using conda.
    [07:34:52] :package: Processed dependencies!
    [07:34:55] :octopus: Pulling code changes from Github…
    [07:34:56] :exclamation:
    [07:34:56] :package: Processing dependencies…
19

Okay the solution was to abandon the conda env and use a requirements.txt file. IT works fine now.

1 Like