25 days ago
I'm having an issue migrating my postgres db for my plio-max project. Here's what the agent provided recommending I reach out. Here's the full diagnosis convo:
Help me fix the failed deployment cb34e3ac-9bde-44df-9eb1-7734f0a0c384. Use the deployment diagnosis tool to see the full diagnostics results. I'll fetch the deployment diagnosis for you. Diagnosed deployment The deployment failed during a volume migration — a Railway infrastructure operation, not a code or configuration issue.
What happened: The Postgres service attempted to migrate its volume starting at 17:02 The migration ran for ~2.5 hours before failing at 19:34 The previous deployment is still online with no data loss
What you need to do: Contact Railway support to investigate and retry the volume migration. This is outside your control and requires platform-level intervention. In the meantime, your Postgres service remains operational on the prior deployment from April 21, so there's no immediate impact.
1 Replies
Status changed to Awaiting Railway Response Railway • 25 days ago
23 days ago
Your Postgres volume migration is failing due to an infrastructure issue on our end - the destination server in us-west is unresponsive, which causes every migration attempt to time out after about 2.5 hours. Your source data is safe and your previous deployment remains online. We're escalating this to our platform team to recover the affected server and retry the migration.
Status changed to Awaiting User Response Railway • 23 days ago
12 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 • 12 days ago