Alarming ! Always-On does not work, script went to sleep twice!

Support Bug Reports
1

Bug description: always on hasn’t woken my repl

Expected vs Current Behavior:

Steps to reproduce:

Bug appears at this link: https://replit.com/@Poubelle404/SimplificationTaches#scripts.py

Screenshot(s)/Screen Recording:

Browser/OS/Device: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.5 Safari/605.1.15

Replit Profile: https://replit.com/@Poubelle404

3 Likes
2

Is the problem that it went to sleep twice or that it didn’t wake back up?

2 Likes
3

Hi @Poubelle404, unfortunately, this is actually how always-on actually works. The way Replit works is that your Repls are on their machines. Replit gets a lot of traffic, so it needs to reshuffle which machine your using every now and then in order to balance this load. As a result, your Repl is stopped, always on just means Replit will immediately run it again once it’s been relocated.

If you’d like your Repl to never turn off, I suggest you look into Replit’s newest feature; deployments.

3 Likes
4

My issue is that it hasn’t turned back on although it should have since the option is ON…

2 Likes
6

Yes, it went to sleep and ignored the always on toggle… basically I’m paying for the always on feature and it doesn’t work.

2 Likes
7

Oh no, that’s not supposed to happen! I’ve reported this to the Replit team and hopefully they can help you out and get this sorted :slight_smile:

3 Likes
8

Hey @Poubelle404!

Can you please try

  • Turning Always On off and then back on for the Repl
  • Running kill 1 in the shell
  • Forking the Repl and making the fork Always On

to see if that helps?

2 Likes