Your photofuture service is currently active with status SUCCESS. The "Deploy Crashed" notification is coming from the previous deployment being torn down, not the new one. When a new deployment goes active, the old one is sent SIGTERM and, by default, immediately SIGKILL'd (since draining seconds defaults to 0). If the old process exits with a non-zero code during this forced shutdown, it registers as a crash and triggers the notification. You can address this by handling SIGTERM gracefully in your application so it exits with code 0, and optionally setting RAILWAY_DEPLOYMENT_DRAINING_SECONDS to give it time to shut down cleanly. If you're using Node.js with npm/yarn as the start command, see this guide as the package manager can intercept the signal.