a month ago
Production deploys of dashboard_mapeamento have been failing since 2026-10-06 18:53 UTC on the pre-deploy command step with: "This deployment expects a volume mounted at /data, but the service has no volume attached."
The contradiction:
Service config shows volume 540a25ab-c8c2-4dd4-b12e-42e356fa330c mounted at /data (5000 MB, sfo region, live state)
Environment status reports hasVolume: true
Last successful deploy 414e3d9e-9450-49dc-a21f-466adc1a92b6 (2026-10-06 17:23 UTC) used identical config and passed pre-deploy, container creation, and volume steps
Commit diff does not touch volume or Railway config
Build completes (pip install, image push successful)
Pre-deploy command (alembic upgrade head) never starts — no deploy logs exist
Failed deployments (same commit 197295bfc660fd2e88ce9b9db4a8e699de44e910, branch main):
4a8ebad8-1f33-4f6b-8828-5ba28b887915 (auto-deploy, 18:53 UTC)
91f2e962-509f-4af3-8c1b-be2f2f9e8cbf (redeploy, 18:57 UTC)
ffaba6f9-e79f-4e07-9602-9fcc5f5a827f (redeploy, 19:01 UTC)
33476272-68ec-4e92-966b-57ea0bfd49bb (redeploy, 19:05 UTC)
All failed with identical message. Dashboard diagnostics classify as infra_error.
IDs:
Project: dashboard-guimas (5bb0d27d-727d-4037-972a-2814dbb8e850)
Service: dashboard_mapeamento (c9fb5ea4-7814-4df4-867e-7c967c9442d7)
Environment: production (056a9786-4164-4d52-bdd6-89bfb2d2fe20)
Volume: 540a25ab-c8c2-4dd4-b12e-42e356fa330c
Impact: Production is serving the previous deploy (414e3d9e), but we cannot publish any changes, including a pending database migration. We have not removed the mount or modified the volume since variables DATA_DIR, DB_PATH, and TOKEN_FILE_PATH point to /data.
Request: Verify why the platform sees no volume at /data when the config shows it mounted. Confirm if any volume check changes occurred between 17:23 and 18:53 UTC on 2026-10-06.
2 Replies
Status changed to Awaiting Railway Response Railway • about 2 months ago
a month ago
Hey! Thanks for the detailed report. We tracked this down to a recent change on our side and we're rolling it back now. We'll update here once the rollout is done.
Your volume and its data are safe. Once the rollback is out, redeploying should go through with your volume mounted as usual.
If you detached your volume or deployed without it in the meantime, reply here before redeploying and we'll help make sure nothing written since then gets lost.
Status changed to Awaiting User Response Railway • about 2 months ago
a month ago
Hey! The rollback is out, and deploys with a volume and a pre-deploy command should go through again. Please redeploy and your volume will be mounted as usual.
Sorry for the disruption, and let us know if anything still fails.
a month 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 • about 1 month ago