9 days ago
When I submit a new commit to GitHub, the new version of my code starts deploying correctly in parallel with the current deployment. However, I recently noticed that the current deployment finishes about 1 or 2 minutes before the new deployment finishes building. As a result, my users lose access to my API during that time. I set a drain time of 30 seconds, but it had no effect. I cannot set an "overlap time" as indicated in the documentation because I do not see this input in my dashboard
1 Replies
9 days ago
The overlap time setting is located in the service's Settings pane (not project settings) under "Deployment Teardown." If you're unable to find it there, you can alternatively set the RAILWAY_DEPLOYMENT_OVERLAP_SECONDS service variable or use config as code with the overlapSeconds field in your railway.json or railway.toml. Note that overlap time starts counting once the new deployment becomes active, so setting it to 120 (seconds) would keep the old deployment alive for 2 minutes after the new one is ready, which should cover the gap you're experiencing.
Status changed to Awaiting User Response Railway • 9 days ago
2 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 2 days ago