Hey there! We've found the following might help you get unblocked faster:

• 🧵 Healthcheck on service serverless wakeup?

• 📚 Serverless

• 📚 Migrate from Fly to Railway

If you find the answer from one of these, please let us know by solving the thread!

Hello!

We're acknowledging your issue and attaching a ticket to this thread.

We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.

Please reply to this thread if you have any questions!

Hello,

We are tracking this issue but we do have it as a listed caveat in our docs that sometimes a redeploy may be needed to wake a service.

https://docs.railway.com/reference/app-sleeping#caveats

I could not see any reference for this on the caveat page.

The service simply stays asleep without any way to wake it up other than redeploy.

This is the caveat:

Slept services still consume a slot on our infrastructure, enabling Serverless de-prioritizes your workload and in remote cases, may require a rebuild to re-live the service.

Unfortunately there's nothing we can do about this in the short-term

In the past 24 it became even worse -
Every 3-4 hours the DB-Service goes to sleep and doesn't wake up and doesnt respond.
I need to re-deploy it every time or Change Serverless False/True to make it back respond.

It works only for a couple of hours and then it doesnt wake up again.
Please advise.

You're right that every 3-4 hours is way too frequent for a production database. The real issue here is that Serverless and databases don't mix well—databases need persistent connections and are almost always active when your app is running, so you're constantly hitting cold boots and connection timeouts.

Your best bet is to disable Serverless on your MySQL database entirely. If you do need Serverless for some reason and your database is only accessed occasionally, the current workarounds (redeploying or toggling Serverless off and on) are what we have available right now.

That said, the jump in frequency you're seeing is worth investigating. If you can share a few timestamps from recent occurrences, we can dig into whether something specific to your setup is causing this or if it's a broader issue we need to address.

❌ The ticket Delayed service startup has been marked as canceled.