We're aware of these transient build queue issues and are actively working on improvements. If you have any queued builds, we recommend cancelling them and waiting rather than redeploying, as additional deploys can compound the queue.

Thank you for the information.

I have a persistent volume attached to this service (bot_data) which contains important application data.

Before attempting to change the deployment region from US West to another region, could you please confirm whether the volume data will be preserved and migrated correctly?

Will all data inside the attached volume remain intact after a region change, or is there any risk of data loss?

Thank you.

When you change the region of a service with an attached volume, the volume is automatically migrated to the new region with your data intact. The migration process backs up the volume, copies it to the new region, and confirms data integrity before mounting it to the new deployment. There will be some downtime during the migration (the duration depends on volume size), but your data will be preserved. We recommend creating a manual backup before initiating the region change as an extra precaution.

i got same issue as well, stuck for create container forever

We're aware of these transient build queue issues and are actively working on improvements. If you have any queued builds, we recommend cancelling them and waiting rather than redeploying, as additional deploys can compound the queue.

Thank you for the information.

I have done additional testing and found something important.

The exact same codebase, environment variables, and configuration deploy successfully in a new Railway project.

The issue only occurs in this specific project/service (heroic-commitment / worker / production).

Because the code works correctly in a fresh project, I suspect there may be an issue with the project metadata, attached volume, or service configuration in this project.

Could you please investigate why this project cannot create containers while identical deployments work elsewhere?

Also, if the issue is related to the attached volume, is it possible to migrate or attach the existing volume and its data to another Railway project without data loss?

The volume contains important bot data and I would like to preserve it.

Thank you.

We can see your volume (bot_data, mounted at /app/data, ~335MB used) is healthy. The container creation issue affecting your project is part of a broader infrastructure issue we're actively working on, and the project-specific behavior you're seeing is noted. Volumes cannot be moved directly between projects, but you can preserve your data by downloading it locally with the Railway CLI using the volume files commands, then uploading to a new volume in another project. We recommend creating a backup of the volume now as a precaution while the container provisioning issue is being resolved.

Yeah im getting the same thing on my project. Please fix this asap!

This is a known issue currently affecting multiple users, and we're actively working on a fix. We recommend cancelling any queued builds and waiting rather than redeploying, as additional deploys can compound the queue.