fix: set Railway drainingSeconds to stop false crash alerts on deploy - #189
Merged
Conversation
Railway gives the old container 0 seconds by default between SIGTERM and SIGKILL when a new deployment goes live. It gets force-killed before it can exit cleanly, so Railway marks it CRASHED and sends an alert email even though the new deployment is healthy. Setting drainingSeconds gives the outgoing container time to shut down before the SIGKILL lands. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TqhW6AhiEriP7nDAEithdw
railway-app
Bot
temporarily deployed
to
PauseAI Catalyse / catalyse-pr-189
July 26, 2026 20:04
Destroyed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Railway gives the old container 0 seconds by default between SIGTERM
and SIGKILL when a new deployment goes live. It gets force-killed
before it can exit cleanly, so Railway marks it CRASHED and sends an
alert email even though the new deployment is healthy. Setting
drainingSeconds gives the outgoing container time to shut down before
the SIGKILL lands.
Co-Authored-By: Claude Sonnet 5 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_01TqhW6AhiEriP7nDAEithdw