a month ago
Hi Railway Team,
We are facing a volume lock issue on Service ID: ed3ea7e3-c8ba-46f5-9882-95c4a9bd1b77 (Project ID: e6320bb0-6626-44e4-8b6e-36dbe952dac6).
Here is the exact history of what happened:
- Initially, our service and volume were running in the US East region.
- We then migrated/moved our service to the Singapore region and deleted/detached the old US volume.
- Now, whenever we attempt to create and attach a fresh 5GB volume in Singapore, the deployment fails with this backend patch error:
"Service would have 2 volumes attached after this patch (e1bdd4a1-e77a-4c4d-96fb-d435410dd3a5, ...). A service can only have one volume."
It seems the old US volume state (ID: e1bdd4a1-e77a-4c4d-96fb-d435410dd3a5) is still stuck in the backend staging/draft configuration and conflicting with any new volume in Singapore.
Could you please forcefully purge/clear all old volume states and draft locks for this service so we can attach a single clean 5GB volume at /app/server/uploads in Singapore?
Thank you!
1 Replies
Status changed to Awaiting Railway Response Railway • 29 days ago
a month ago
No stuck state to purge, the good news is this is just a timing thing. When you deleted the volume, it wasn't removed immediately. Volume deletions have a 48 hour grace period so they can be recovered, and during that window the volume is hidden from the canvas but still counts as attached. That's why creating a new one fails with the "2 volumes" error.
The deletion completes on July 25 at 08:59 UTC. After that you can attach a fresh volume in Singapore.
One thing worth knowing before you wait: the volume you deleted had already moved with the service. It's a 5GB volume in Singapore, mounted at /app/server/uploads, which is exactly what you're trying to create. If you'd rather we restore it so you can use it right away, reply here and we'll bring it back.
Railway Team
Status changed to Awaiting User Response Railway • 29 days ago
22 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 • 22 days ago