16 days ago
Hello team, I'm facing a unique issue. Serverless function was working perfectly well when I was using Hobby plan. But now that I have pro plan for a few months, I am noticing that the instance does not sleep even when serverless is enabled. For reference, I've deployed the instance on EU metal. I'm also using Redis instance paired up with my original instance.
Usually I'd have assumed that Redis might be keeping the connection open but we never faced this while on Hobby plan with the same stack. So Redis connection most probably is not the issue.
3 Replies
16 days ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
16 days ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open brody • 16 days ago
16 days ago
It’s unlikely the tech stack itself, what matters is whether anything in your code or setup changed between your old Hobby deployment and your current PRO one. Even small additions like telemetry, analytics, health checks, uptime monitors, or private networking between services can generate enough activity to keep the instance awake. have you made any code changes between your hobby plan to your recent swap to your pro plan? heres the railway docs https://docs.railway.com/reference/app-sleeping for reference
11 days ago
Hey @monuit , thanks for the response. We just figured out sentry uptime monitor was keeping the server alive. Thanks again
Status changed to Solved ray-chen • 11 days ago