Redis migration confusion

[toxic sorrel]

Hello,

I clicked the migrate button in Redis and it failed the first time and seems to have worked the second time.

My confusion though lies in which redis instance is the new migrated one. When I click "View Next Steps" and then "Go to new database" it takes me to "Redis Legacy" on the canvas (very confusing if this is actually the new migrated redis instance). I used to have one redis on my canvas and now I have 3:

https://share.cleanshot.com/pCVbncnD

1. Which is the new one I need to point my app at?
2. Which are the old ones I need to delete?

Thanks for the help.

[swift parcel]

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

[tropic grail]

Project ID: 16bf5d62-bf3b-40bc-9df7-4472c0e309c3

[toxic sorrel]

16bf5d62-bf3b-40bc-9df7-4472c0e309c3

[rose adder]

you migrated at a bad time, not your fault what so ever though, right now i can tell you that the left database is your original

[old rune]

This is likely related to the ongoing incident. #🚨｜incidents for updates

You should be able to hit the migrate button again after we reactivate it

[rose adder]

for now you can delete the other two (the ones with the volume) and then once the incident is over you can try the migration again

[toxic sorrel]

I appreciate the help @rose adder, but is this the official recomendation from railway @old rune ?

[rose adder]

i dont work for railway, but thats what im recommending because the migration was ran during the incident so theres a good change theres issues with those two new redis databases, better be safe than sorry, your original database is still in tact on the left

[old rune]

This advice seems solid to me, but we will be communicating best next steps more clearly after the incident is resolved

[rose adder]

@toxic sorrel - could you try agian now, should be fixed

[toxic sorrel]

@rose adder just successfully retried and it worked. Thanks guys!