3 hours ago
This seems to come up often in railway support threads (here, here, and others), but the advice is always just "redeploy" (literally not an option for failed deployments in the UI) or "push another commit" (requiring a full change -> review -> staging -> release cycle).
The "restart policy" causes it to just do this same failure for the number of retries.
It's not like this is happening every day, but when it does during production deploys, it causes an outage for services don't have a healthcheck configured (that one is on me, workers need healthchecks too).
Can we get a more permanent fix for this issue?
2 Replies
Status changed to Awaiting Railway Response Railway • about 3 hours ago
34 minutes ago
This is a transient build failure that resolves on its own - a subsequent deploy of the same code will succeed. We understand it's disruptive when it hits a production deploy.
You're right that healthchecks are the key protection here. With a healthcheck configured, a failed deploy never replaces the running deployment, so the production impact goes away. Adding healthchecks to your worker services will close that gap.
For retriggering a deploy after a failure, you can use the three-dot menu on the most recent successful deployment to redeploy from there. Your broader point about wanting this to not happen in the first place is well taken.
Status changed to Awaiting User Response Railway • 34 minutes ago
sam-a
This is a transient build failure that resolves on its own - a subsequent deploy of the same code will succeed. We understand it's disruptive when it hits a production deploy. You're right that healthchecks are the key protection here. With a healthcheck configured, a failed deploy never replaces the running deployment, so the production impact goes away. Adding healthchecks to your worker services will close that gap. For retriggering a deploy after a failure, you can use the three-dot menu on the most recent successful deployment to redeploy from there. Your broader point about wanting this to not happen in the first place is well taken.
6 minutes ago
Actually, I dug into this service. It has a healthcheck. But also, this failure was during the build step, not deploy and yet it still removed the current deployment.
Status changed to Awaiting Railway Response Railway • 6 minutes ago