a year ago
Similar to ThallesComH, I've started the migration of a volume from US West (metal) from US East (metal) and it took 20 minutes so far. The volume has ~300 MB.
Project ID: be3f2db8-13c1-4dfb-b758-fbaace10701c
16 Replies
a year ago
!t
a year ago
This thread has been escalated to the Railway team.
Status changed to Awaiting Railway Response medim • about 1 year ago
a year ago
I've had to clone the database from backups. The old service is still being migrated (15004f78-e788-4043-9b55-30dc19deae19, named "Postgres-old"). I hope this doesn't eat my credits
a year ago
Could you go to https://railway.com/account/feature-flags and show a screenshot of it?
We think you have a beta flag on that isn't supposed to be there
a year ago
No worries about credits, I've added $20 to your account. Apologies for the inconvenience
Thank you! By the way, the service is still being migrated. Weird that it didn't time out or something
a year ago
Do you have any valuable data there, or are you okay with a the backup?
I backed it up before migrating, and the client didn't find anything missing, so it should be fine to delete Postgres-old
a year ago
👍 could you try deleting the service+volume?
Apologies about this. Your volume was created using a beta flag that we've since removed, so it's stuck in some weird state that is hard for us to undo at the moment.
a year ago
Hi Juan, glad to see this worked! Will confirm with the team if we cleared that one out for you specifically, but just wanted to know if you took any actions on your end?
Status changed to Awaiting User Response Railway • about 1 year ago
a year 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 • about 1 year ago