2 months ago
I am currently using the free plan and facing an issue with my project deployment. The deployment keeps failing because the replica configuration is set to 2 in the region (us-west2), but the free plan allows only 1 total replica.
I have already updated my railway.json file to set numReplicas to 1 and sleepApplication to true. I also tried resetting the scaling using the CLI, but the configuration still appears to be stuck with us-west2 = 2, which is causing the deployment to fail.
Since I am unable to change or reset this configuration from my side, I kindly request you to please reset the replica configuration for my service to 1 replica.
Project details:
Project Name: Sendy
Environment: production
Service: web
Repository: anupamkayal/Sendy-custom-url
I would really appreciate your help in resolving this issue.
Thank you for your time and support.
Best regards,
Anupam Kayal
1 Replies
Status changed to Awaiting Railway Response Railway • 2 months ago
2 months ago
Solution for Replica Configuration Stuck on Free Plan
This is a known issue on the Free plan when numReplicas gets stuck at 2 (or any value >1).
Quick Fixes to Try (in order):
- Remove the multi-region / replica config completely
- Delete or comment out the entire deploy section in your railway.json file.
- Push the change to trigger a new deployment.
- Force reset via CLI Run these commands: Bash
railway login
railway project select # select your "Sendy" project
railway service select # select the "web" service
railway scale 1 # set to 1 replica - Alternative: Delete the deploy config via Dashboard
- Go to your web service → Settings → Config as Code.
- If railway.json is linked, temporarily unlink it or set numReplicas: 1 and sleepApplication: true again.
- Redeploy.
- Nuclear Option (if above fails)
- Create a new service in the same project using the same GitHub repo.
- Point it to the same branch.
- Once the new service deploys successfully with 1 replica, you can delete the old "web" service.
The Free plan strictly allows only 1 replica total. Railway sometimes caches the old scaling config, which is why railway.json alone doesn't always fix it.
@team — if the above doesn't work, please reset the replica config for project Sendy (service: web) to 1 replica in region us-west2.
Let me know the result after trying steps 1–3 (especially the CLI railway scale 1).
Hope this gets your deployment running again quickly! super grok✊