a month ago
Staging service stuck — volume pinned to unavailable node in sfo region
Service: courtvibe-staging (ID: 90c8fa2b-009e-4c2a-a38d-f7d4a87fa61b )
Build succeeds every time but Deploy → Create container fails after exactly 22-29 minutes with “Failed to create deployment”. Railway’s own diagnosis tool confirmed: “The volume mount at /app/data may be pinning the service to a node that is no longer available.”
8 consecutive failures since Jun 8 11:11 PM HKT. Posted on Station 10 hours ago with no response.
Can someone migrate or detach/reattach courtvibe-staging-volume from the dead node?
3 Replies
“This deployment failed due to a platform infrastructure issue that requires Railway support to resolve. The build completed successfully every time, but the container scheduler has been unable to provision the container in the sfo region across 7 consecutive deployments since June 8.
The volume mount at /app/data may be pinning the service to a node that is no longer available. “ zero response from railway support !