2 years ago
App Sleeping worked without issues for the last weeks. Calling the url of an app was delayed for a 1-2 seconds and then the app showed up.
Today I've noticed that calling the url of a sleeping app showed a railway error screen. After several seconds and reloading the page the app was up again. Showing the railway error screen is a bit annoying for low traffic apps.
Is this intended or an error?
10 Replies
2 years ago
this is likely an unintended side effect of the added ddos mitigations that where recently added to the proxy, railway is working on a new http proxy that should solve this issue
awesome! I just added app sleeping to an app to save costs and I was confused why it wasn't working
2 years ago
it works, just doesn't come online without showing the error page first
2 years ago
something something health detection propagation delays
2 years ago
For us the problem still exists: Apps in "app sleep mode" are showing the error page ("Application failed to respond"), thereafter the app works. It would be cool if the initial request would take just a little bit longer without the error page, because we have some apps which are seldom used and we could save costs & energy with app sleep mode.
2 years ago
that's an entirely new issue specific to the v2 runtime, fixing it is deprioritized until they fully roll out all V2 features
a year ago
Hello all!
We've resolved an issue where apps with longer startup times were showing 502 errors. Apps now have up to 10 seconds to start accepting traffic, thus preventing these error pages from appearing.
You will need to trigger a deployment so that the changes we have made take effect.
a year ago
cc @jeasx & @Sr Izan
a year ago
it could be avoided if your app woke up fast enough, but now we continue trying for up to 10 seconds