Project: victorious-forgiveness, Service: -earbuddies-server, Environment: production.

Our service's replica count is currently set to 2, and it has a persistent volume attached (mounted at /data). Every deployment now fails at the "Deploy > Create container" step with:

"Replicas are not supported if you have a volume attached to your service."

This has been failing for roughly the last 12+ hours - we believe our own autoscaler script called the Railway API to raise replicas from 1 to 2 in response to a load test, which put the service into this state. The dashboard's own Settings > Scale > Replicas field is now greyed out/disabled and we can't edit it back down to 1 ourselves, so every deploy since then has failed and the service has been running on an old build the whole time.

We do NOT want to remove or detach the volume - it holds real persistent data we need kept intact.

Could you please force the replica count back down to 1 on our end (or unlock the Settings field so we can do it ourselves)? We just need deploys to succeed again without touching the volume/data. Happy to provide the exact deployment IDs that failed if useful. Thank you!