Yesterday, I triggered the re-deployment of a previously error-free Railway service with a simple code change in the linked GitHub repository. Then, the deployment for this service was stuck more than 7 hours in the "Deploy" stage (without any log output), so I ended up aborting the stuck deployment process.

Now, I reverted the code changes in a separate commit, pushed this to GitHub and thereby triggered another deployment of the service. This deployment (and all subsequent trials) are now stuck apparently indefinitely in the "Queued" state with the info "Waiting for volume migration."

The Railway service does have a volume attached. Also, I've run into similar problems before (around 1 month ago, I was also indefinitely stuck in the "Waiting for volume migration" step) and ended up completely duplicating the service – which worked at the time, because the service did not contain any production data in its volume, but which would not be applicable for me in the future when the Railway service's attached volume does actually contain production data (because duplicating the service incl. its volume config does not duplicate the volume data).

Can you please check why the deployment of the service is stuck in the "Queued" state with the info "Waiting for volume migration"? Also: Is there anything I can do in the future to avoid running into these problems again? I fear that when I store production data on the service volume, I might run into the situation that I cannot push any new code changes and am stuck with the old service's deployment if I want to keep the existing data without migrating to a completely new Railway service instance just to get around the "Waiting for volume migration" problem.

Thanks in advance for helping out!