Same for me. Why those Railway-initiated redeployments? Why do they fail?

Same for me. Volume was already migrated to new region (if that's the reason of this automatic trigger) but results in "Volume migration failed". I did a "retry deployment" and it went through succesfully.

Now I have a second volume trying to migrate with "Waiting to migrate to new region.", which is already in the Metal/europe new region, it's been more than 60minutes, for ~150MB, and still "waiting to migrate"

I’ve also had two Postgres deployments fail.

Same for me, it also happened on a Qdrant instance (as for a postgres instance, and 2 different environment with a Postgres on each of them)

same here.. is there some info about this somewhere? was this a scheduled thing that I wasn't aware of?

!t

also.. it's pretty weird to have the message

Volume migration failed.

There was an error migrating your volume to the new region.

when i wasn't aware that my volumes were being moved to a new region.. which region is it going to?

is it related to migrating to metal? my volumes were already on metal..

redeploying didn't resolve the volume migration error btw..

That's just a generic error message. They are likely using the same mechanisms for this as region to region moves.

Same for me. I got random database deployment which was failed and no logs. But the app works as expected.

Same issue. My case: In two of my projects, postgres and redis are affected. App works, but I can't reach the tables in Postgres/Data on the dashboard.

Hello,

okarmazin, I have raised your migration failure to the team.

For everyone else, please provide direct links to the service that has a failed migration.

@Brody to each service? in all environments? basically for me, it's every service in every environment that has an attached volume

actually, one of them didn't fail.. so it's 5 services in total, should I link them all?

yes please

https://railway.com/project/58cd7410-04d6-4c6e-a74d-fa7c78455231/service/ade6159a-a640-4f0d-b8b8-44dc80f7c770/data?environmentId=2d4912ad-d701-4872-994e-f32abb7f7b48
https://railway.com/project/58cd7410-04d6-4c6e-a74d-fa7c78455231/service/bbaa4d1d-0308-42f6-af70-fdb46f52f6b2/data?environmentId=2d4912ad-d701-4872-994e-f32abb7f7b48
https://railway.com/project/58cd7410-04d6-4c6e-a74d-fa7c78455231/service/e5de860e-c1a7-4322-90c9-3472876b77c2/data?environmentId=2d4912ad-d701-4872-994e-f32abb7f7b48
https://railway.com/project/58cd7410-04d6-4c6e-a74d-fa7c78455231/service/e5de860e-c1a7-4322-90c9-3472876b77c2?environmentId=7809a736-5e75-42e0-846f-b3b17dac958e
https://railway.com/project/58cd7410-04d6-4c6e-a74d-fa7c78455231/service/ade6159a-a640-4f0d-b8b8-44dc80f7c770/data?environmentId=7809a736-5e75-42e0-846f-b3b17dac958e

https://railway.com/project/34849d22-d685-4e73-8858-fbd4fe42ea65/service/24cfdad6-9505-4495-9c38-ce1a7682e430?environmentId=6f50724d-82da-4465-8eac-edecbd1f809a&id=20ad4717-8229-409b-b344-960032fe9430

https://railway.com/project/36300550-6af0-468b-b469-81b8474d7459/service/fc5ea55b-02a0-478c-af49-65a74c2a6527?environmentId=f9de6805-f9ac-4a2c-ba9e-ba412d217539
https://railway.com/project/36300550-6af0-468b-b469-81b8474d7459/service/6b71c6ce-3a50-4408-9aca-9c3e8a2a055e?environmentId=f9de6805-f9ac-4a2c-ba9e-ba412d217539

https://railway.com/project/5f4b873a-417b-4a5e-8d3d-f38683102fec/service/fa4c0139-6567-4fb3-8d04-9252501d4171?environmentId=79212791-3b90-4ea3-88cd-c6c6706855a3

is there an updated status on this issue?

On my side, I already migrated everything to Metal 2 or 3 months ago.

However in the past few days, I got 4 or 5 automatic deployments from railway telling me my services were being migrated to metal. Either volumes (where migration failed but was already on metal) or services (reporting successful metal deployment but was already in metal prior).

I think everybody in this thread has already moved to Metal months ago.

yes, moved to metal months ago, but my postgres volume still has a volume migration failed sticker on it.. is it safe to redeploy the service and will that resolve the volume migration failed error?

without data loss 😄

!s