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

• 📚 Deployment Actions

• 🧵 Bun project with node-canvas not working

• 📚 Production Readiness Checklist

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

Apologies but this looks like an issue with the application level code. Due to volume, we can only answer platform level issues.

I've made this thread public so that the community might be able to help with you query.

Hi @jake! Thank you for the response. I guess I will keep this thread open if someone else see this issue later with their projects.

I'm not sure that's an application code issue since I do just "process.exit(0)", so I will see if this will occur again

The 0 passed as an argument in the exit code indicates a successful execution or no errors so may be that's why the restart doesn't happen.
Try non-zero values.

@smolpaw That's not quite right according to this documentation: https://docs.railway.com/guides/restart-policy .

>Always: Railway will automatically restart your service every time it stops, regardless of the reason.

I just had this happen one more time, my deployment had status "Completed" and not restarting. But my restart policy is set to "Always".

UPD:
Just tried it with another deployment by doing "process.exit(0)" on purpose and it seems to restart it as expected.

I wonder why its not working for my main deployment with same configuration and showing instance just as "completed"