Documentation page
Config as Code Reference: https://docs.railway.com/config-as-code/reference#draining-seconds
Current example
"deploy": {
"drainingSeconds": "10"
}
Actual behavior
Using the documented string value in railway.json causes the deployment to fail before startup with:
Failed to parse your service config. Error: deploy.drainingSeconds: Expected number, received string
This was reproduced on July 21, 2026 with the current Railway deployment parser.
Accepted configuration
Changing only the value type to a JSON number is accepted:
"deploy": {
"drainingSeconds": 10
}
Suggested change
Update the example to use a numeric value so it matches the production parser. The overlapSeconds example immediately above may be worth checking as it is also currently shown as a string.
Documentation page
Config as Code Reference: https://docs.railway.com/config-as-code/reference#draining-seconds
Current example
Actual behavior
Using the documented string value in railway.json causes the deployment to fail before startup with:
This was reproduced on July 21, 2026 with the current Railway deployment parser.
Accepted configuration
Changing only the value type to a JSON number is accepted:
Suggested change
Update the example to use a numeric value so it matches the production parser. The overlapSeconds example immediately above may be worth checking as it is also currently shown as a string.