Hello,

You have yet to apply the change to disable app sleeping -

Best,
Brody

Thank you !

Could be just me, but i am confused by this. In the docs is says that serverless is the new name for app-sleeping, and severless is disabled.

Also, i can see you changed this sleep application setting for me (thank you) but where do i see/change it?

Ah, I think you are saying that i didnt deploy the change (but that i made it) I had servless switched off before, but flipped it on and off again before submitting my post. So it seems like it was initiated in a null state even though it showed as off. Maybe that was issue.

It was enabled when you opened this post, all that was required was deploying the changes!

I am positive that before, it at least showed in the UI as off. Even after deploying with the change, if i flip the serverless from off -> on -> off, i get the same "changes made" display. with enable sleeping going from "" -> false. Gif attached

Seems like no matter what I do, the config for sleeping is stuck at null

The service is not currently configured to sleep.

Yes, the problem is that it does sleep. Im trying to figure out why

despite the fact the the UI shows serveless as off.

My hypotheis is: the strange behaviour depicted in the gif is pointing to the config being in a bad state.

But you would know better than I.

I have checked the backend and sleepApplication is set to false.

What makes you think it is still going to sleep?

After periods of prolonged no use. We would see requests hang and no sign of receiving them from the service.

I am fairly confident that serveless was disabled long before this thread.

But let me wait until the next occurrence to make sure that we didnt fix it here. Will report back.

Hello,
I’m experiencing an issue similar to this thread: Service sleeping even when serverless is disabled. In my case, my backend fails to reach the Postgres database after running for a few hours, even though Serverless (App Sleeping) is turned OFF in the settings. I’m currently on the Free plan, and this issue makes me hesitant to continue using Railway.

My backend initially connects correctly to the internal Postgres (postgres.railway.internal) and works fine for about ~1 hour, but after that it can no longer reach the database.

i had to change the database private network to making things works again internal networking have little bugs it think

Hi,

I have the same issue.

I'm testing the service and am on a Trial Plan now.

I have no pending deployments, serverless is disabled yet the app is asleep now.

Cheers

Jakub

I did not want to wake up the test app by visiting the URL but now I did and I got an "Application failed to respond" error instead of about 10sec response time for the first request.

Request ID: 7lU3A45pTsWpXQf-0-QtfA

Hello,

You seem to have had a similar problem. How can I change the postgres connection to private? I thought the postgres.railway.internal is the private one.

Cheers,

Jakub