Hi,
I have three Repels, all Discord Chat bots. I use Cycles to keep two awake, and the third should stay always-on because of my account, however the non-cycle bot keeps turning off after a few minutes. The other two remain active 24/7.
The bots are identical in operation, have had no code updates in the last 6 months and the issue has only started in the last week. There are no error logs when I open the repel.
Why is the third turning off?
I have a repl that is supposed to always be on, but sometimes something happens with the execution (could be a bug) and the program goes down and doesn’t restart. It only happens about once every week or so. I was wondering if there was a way to make it automatically restart when this happens?
I tried to follow what they suggested in here:
https://replit.com/talk/ask/restart-on-error/43781
and changed my .replit file to have this line:
run = "while true; do npm start; sleep 2; done"
but it didn’t seem to work. Any other suggestions to get a repl to restart itself when execution stops?
bump @devs, any suggestions?
there are no devs, but this is a normal thing. Always on is technically a lie and you can’t restart it. period. That’s because that’s how replit works no matter what thread you run on your core (not main thread) or try to ping it, replit will force shut all repls off after x amount of inactivity so there’s literally nothing you can do because it’ll just turn off. The best you can do is try running an external pinger but even those have been rumored to soon stop working
My code executes once a minute, there isn’t any inactivity. The repl used to run for weeks at a time before it ever had issues, but lately it’s turning off like every hour or two.
I’ve noticed the same thing two of my repls with always on. I believe replit has changed something on their side that’s turning them off, they used to run just fine and I haven’t changed any of the code
Honestly it’s barely even every hour now, it’s like every 20 minutes. Pretty much making my repl unusable. Gonna have to find a new tool which is annoying
Hey all, would you be able to send me links to some of the repls where you’re experiencing this so we can take a closer look?
And just for clarity, from the docs:
All Repls are subject to go to sleep at any time. However, Always On will immediately run your Repl again whenever this happens.
https://replit.com/@Virtualjohn/Digital-IB-Converts This has turned off at least 5 times for me today alone (and not turned back on)
Hi,
I have three Repels, all Discord Chat bots. I use Cycles to keep two awake, and the third should stay always-on because of my account, however the non-cycle bot keeps turning off after a few minutes. The other two remain active 24/7.
The bots are identical in operation, have had no code updates in the last 6 months and the issue has only started in the last week. There are no error logs when I open the repel.
Why is the third turning off?
As far as I know replit is moving away from always on replits to deployment model on the cloud to give node.js / server related replits better stability.
https://blog.replit.com/deployments-launch
But there is not yet any official information what happens to always on feature but I highly suspect they are not going to fix and improve always on feature anymore that they have this better deployment feature that do hosting better.
That doesn’t quiet explain why some Always-On repels are working, but one is not when the only difference is using cycles. Unless Replit is now prioritizing the extra money I’m spending over the monthly fee I also pay?
I have the same issue! I just made a post about this. Their NIX migration really made things a mess
"Always On" repl getting stopped my post
Fact is if I’m honest that:
Replit is not very mature service and it is constantly developed this means that there will be more issues than other hosting services. It is just how these things work. if stability is important for you it would be better host your bots in some boring web hotel that only use LTS patches in everything and have barebone features and rarely patch any new features.
But if you like rapid level of new features and innovative technology and accept that there will be more issue and you quite often beta-test these features then staying in replit is solid option.
On the good side as development IDE replit works pretty well most of time and prototyping web servers and sites work pretty well if you can tolarate more down times. 
Hey all!
I greatly apologize for the issues you are having with Always-On. We are actively investigating this issue, so please send us the links to any Repl that has Always-On and isn’t working so we can look into this!
There was a glitch between our web server and our platform infrastructure. If you turn Always-On off and then back on, it should fix it. We apologize for this issue!
Shane, does this mean that always on are always on as so far they always get shit down after a while.
No, Always-On Repls should not shut down for good. However, Always-On does not stop your Repl from being restarted once in a while. This happens to conserve resources, but once your Repl is restarted, it will stay up for as long as it can before we need to shuffle the containers around again.
TL;DR: Always-On Repls will restart, but they should never stop indefinitely.
Just wanted to come back to this thread and say thanks to the devs for fixing! Not often you get a resolution this quickly. Appreciate it!
No problem at all! Please don’t hesitate to let us know if anything else comes up!