Dropped requests when App Sleeping enabled?
Based on my understanding from the docs (and how I'd expect this feature to work), app sleeping is supposed to keep a request that hits a sleeping instance dangling until it's woken up, then resolve it. First question: is that right?
If yes, it doesn't seem to be working. I have a Node API deployed on Railway with app sleeping enabled. Once it goes to sleep and I make a request, I get an "Failed to respond" error. Eventually after a few more tries the application woke up, and the request goes through.
I thought maybe the problem was the lack of a health check, but I added this and it hasn't made a difference.
What am I missing?
9 Replies
Project ID:
56cafcfa-394c-46c9-a811-dc3207bad3dc56cafcfa-394c-46c9-a811-dc3207bad3dc
To your first question, yes that's how it's supposed to work.
We are aware it's currently not working as designed and we have an internal ticket for it, but right now it's unfortunately not the highest priority as it can be solved by disabling app sleeping.
for your reference the health check does not come into play when waking an app.
I see, thanks for the info. Was hoping to enable it for all the services we create for PR environments since we can have many of those at a time and those services obviously rarely receive traffic. Hope to see it resolved soon 🖖
I've added your discord thread to our internal ticket so that I'm able to follow up here when it's fixed!
great, thanks!
No problem!
New reply sent from Help Station thread:
Hello,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.You're seeing this because this thread has been automatically linked to the Help Station thread.
cc @json & @Aurélien