18 days ago
I'm having an issue with Railway. My Discord bot deploys and starts successfully. The logs show that the bot comes online, registers slash commands, loads the database, and continues running normally for several minutes.
However, every time I deploy a new version, Railway sends me an email saying:
"Deploy Crashed!"
In the logs, I only see:
npm error signal SIGTERM
followed by:
Stopping Container
I do not see any JavaScript errors such as SyntaxError, TypeError, or ReferenceError.
The bot works correctly after deployment and remains online. The "crash" only seems to happen when Railway stops the previous container during a deployment.
Why is Railway marking the deployment as crashed and sending crash emails when the bot appears to be running normally?
2 Replies
18 days ago