2 months ago
Application logs are fine, nothing suggests an error
Re-deployment helps but temporarily
It started yesterday, re-deployment helps, but it keeps dropping almost every hour or so
Attachments
4 Replies
2 months ago
It might be a bug in the app that I confused with the recent Railway problems.
Pls close this thread for now.
Status changed to Solved nico • 2 months ago
2 months ago
I can't trace the error in my app.
The behavior is pretty consistant: after about 1 hour after deployment, app is starting to throw 502
I can see it in railway's http logs, but everything is fine in application/deployment logs.
@Railway please help
Status changed to Awaiting Railway Response Railway • 2 months ago
2 months ago
check your service's metrics tab on railway and look at memory usage over time, specifically in the hour before the 502 hits. if you see it climbing steadily that tells you a lot. also check if you have a health check configured on railway, if the endpoint is slow or not responding railway will mark the service as unhealthy and serve 502s
2 months ago
those two things are the most likely culprits given what you're describin