Looks like you have an active deployment now?

Hi Brody,

Thanks for checking. The app is currently running (the deployment from ~23 hours ago is active), but we're still unable to deploy any new code. Every new deployment fails at "Deploy → Create container" with "Failed to create deployment" within a few seconds — even after a full build completes successfully.

The pattern:

• Build: succeeds (~40s)
• Deploy → Create container: fails immediately (~3s)
• The currently running container stays active (no downtime)

We have Teardown enabled. The service has a Volume (pr-valuation-volume) mounted at /data (ReadWriteOnce). Our suspicion is that the volume lock isn't being released properly before the new container tries to mount it — but we're not sure if that's on our end or a platform issue.

The practical problem: the running container was started before we updated the ANTHROPIC_API_KEY variable, so it's running with an outdated key. We need to redeploy to pick up the new variable, but every deploy attempt fails.

Is there anything on the Railway side that could cause "Create container" to fail consistently on this specific service? And is there a way to force-restart the current container so it picks up the new environment variables without a full redeploy?

Thanks

Have you tried manually removing the current deployment and then deploying again via the CLI?

"We tried that — removed the active deployment and ran railway up immediately. Same result: Build succeeds, Deploy → Create container fails in 2 seconds. The app is now completely down. We need to create a new service — can you help us detach the volume so we can reattach it to a new service safely?"

You can detach and reattach volumes yourself from the dashboard or CLI. No action needed from our side for that.