By default, Railway have restart policy enabled, it will restart on failure 10 times, probably something is not ready when the first try of deploy and succed on the next one, do your deployment relies on another service that is serverless?

Not sure.

Hi @mayori, thank you! No other service as far as i know. Do I have a way for the deploy to wait for everything to be ready?

No, but if this issue persist, you can disable the Restart Policy on your service settings and take a few minutes before redeploy, this will prevent restart and you'll be able to see the actual error

I'm not seeing anything about the deploy restarting, to be honest, in the logs - it's failing and succeeding the first time

Is this a Node project?

onsuceeding Yes, it is

Try this: https://docs.railway.com/deployments/troubleshooting/nodejs-sigterm-handling

Thank you, but I'm already using node server/start.js as start, not npm.

1 of 2 fails, but if I go and click the crashed one, it's in fact deployed successfully.

Nothing? How can I raise it with @Railway support ?

...