Repository navigation
fix: keep Railway services awake - #47
Merged
Merged
Conversation
App sleeping was switched on for Gateway and Web in both environments after the Config as Code cutover. A sleeping Gateway pauses its retention, billing and analytics schedulers and gives MCP clients a cold start, so declare sleepApplication: false for both services. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
App sleeping (
sleepApplication) is nowtrueon Gateway and Web in both environments. Every deployment that succeeded before today's Config as Code cutover had itfalse, so it changed during the migration: either during theconfig applyor when the Config File paths were changed in the dashboard.The running deployments still have it off, but the next build of each service will sleep when idle. For the Gateway that pauses its usage-retention, Stripe-reconciliation and analytics-rollup schedulers, and gives MCP clients a cold start on the first request after idle.
Change
.railway/railway.ts:sleepApplication: falsefor Gateway and Web, so config as code owns the setting.Plans (read-only)
deploy.sleepApplication(true → false)After merge
Run
railway config plan && railway config applylinked to dev, then production.🤖 Generated with Claude Code