Skip to content

fix: keep Railway services awake - #47

Merged
CountableNewt merged 1 commit into
devfrom
fix/railway-no-app-sleep
Sep 28, 2026
Merged

CountableNewt merged 1 commit into
devfrom
fix/railway-no-app-sleep

Conversation

@CountableNewt

Copy link
Copy Markdown
Collaborator

App sleeping (sleepApplication) is now true on Gateway and Web in both environments. Every deployment that succeeded before today's Config as Code cutover had it false, so it changed during the migration: either during the config apply or 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: false for Gateway and Web, so config as code owns the setting.

Plans (read-only)

Environment Plan
dev 0 add, 2 change, 0 destroy: Gateway and Web deploy.sleepApplication (true → false)
production 0 add, 2 change, 0 destroy: the same

After merge

Run railway config plan && railway config apply linked to dev, then production.

🤖 Generated with Claude Code

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>
@CountableNewt
CountableNewt merged commit ecb36d6 into dev Sep 28, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant