Hello Railway Support,

A previous attempt to migrate our production Postgres service to another region failed or was aborted. The database remained online afterwards and continues to serve production traffic normally, but the Railway canvas has permanently displayed “Migration failed” beneath the Postgres service ever since.

The active database, our production web service, and scheduled sync jobs are currently healthy. We do not want to retry the region migration or modify the active volume merely to remove this status.

Could you please:

1. Inspect the failed migration state and identify whether it is stale control-plane metadata or an unresolved volume issue.
2. Clear or repair the “Migration failed” state without remounting, restoring, migrating, or otherwise modifying the active production volume.
3. Confirm whether backups, snapshots, resizing, and future recovery operations are affected by this failed migration record.

I have attached a screenshot of the current Railway canvas state. Please let us know if you need the approximate date or source/target regions of the failed migration.

Thank you.