a month ago
I get a “Deployment crashed” alert only when I start a new deploy, and the alert is always for the old deployment that gets replaced and then marked as Removed. The service has an attached volume, and the new deployment becomes healthy.
Is this expected behavior, or a false-positive notification? Can this alert be disabled for old deployments during redeploy?
This happens only to service with attached volume.
On the logs it shows only:
Stopping Container
Stopping Container
1 Replies
a month ago
This is a known behavior for services with attached volumes. Since a volume can only be mounted to one deployment at a time, the old deployment's process is forcefully stopped when the new one takes over, causing it to exit with a non-zero exit code, which triggers the crash notification. There is currently no way to suppress crash notifications specifically for replaced deployments. You can try setting RAILWAY_DEPLOYMENT_DRAINING_SECONDS to give the old deployment time to handle SIGTERM and exit cleanly (exit code 0), which would prevent the crash status and the associated notification.
Status changed to Awaiting User Response Railway • about 1 month ago
Status changed to Solved vikegart • about 1 month ago