Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pro+ Runtime immediately stops executing, Message: "Waiting to finish the current execution", Runtime: "Connecting", whenever browser closes. #4666

Closed
MichaelShawJ opened this issue Jun 29, 2024 · 4 comments

Comments

@MichaelShawJ
Copy link

Describe the current behavior
I can delete and start a new runtime. It will run fine, executions happening twice per second. As soon as I exit the browser or the computer goes to sleep, the code snags and says Message at bottom of screen: "Waiting to finish the current execution", and the Runtime message in the top right says: "Connecting", whenever browser closes. The code, which should take 2 hours to run, is stalled an unrecoverable. It does not finish execution. All the data is lost.

Describe the expected behavior
Because I am a Pro+ subscriber/user, I would expect the Runtime to continue even when I close the browser, for up to 24 hours.

What web browser you are using
Chrome

Additional context
Link to a minimal, public, self-contained notebook that reproduces this issue.
https://colab.research.google.com/drive/1yzCA91IgLgFBvpDMKgLvY78z2oiuHYZ4?usp=sharing

@juliocesardaxavante
Copy link

Yes, this problem is happening to me too and other users. Please Colab team: we need feedback on the normalization of this service. I'm wasting a lot of time restarting my project several times a day.

@Mitali-N
Copy link

did this get resolved? I just bought Pro+ for background execution, and I, too, am facing runtime getting disconnected as soon as the computer goes to sleep.

@cperry-goog
Copy link

Can you file feedback in product and reference this issue and we can take a look?

Copy link

Without additional information we're not able to resolve this issue, so it will be closed at this time. You're still free to add more info and respond to any questions above, though. We'll re-open the issue if you do. Thanks for your contribution!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants