22 days ago
Hello Railway team,
I'm experiencing a repeated build failure when deploying an updated Python FastAPI application through GitHub.
Project: picklemix-backend-staging
Environment: production
Service: picklemix-api
Git branch: rebuild-missing-latest-changes
Release: v1-368-scheduling-correctness-and-error-classification
Git commit: 0e56398
What happened:
The first deployment failed during "Build > Build image", before any Python dependencies were installed.
Railway's built-in diagnosis reported an Infrastructure Error and recommended redeploying the same commit because the build stopped immediately after the build plan was printed, without logging an application error.
I retried the failed deployment, but the second attempt also failed during image building.
Failed deployment IDs:
- 15afda57
- dde58878
The second deployment's Build Logs contain only:
"All aboard, next stop: builder v4"
Build configuration:
- Builder: Railpack
- Python FastAPI application
- Procfile command: uvicorn app_api:app --host 0.0.0.0 --port $PORT
- Dependencies installed through requirements.txt
The previous v1-367 deployment remains active and healthy.
The deployment was triggered automatically from GitHub. No build-configuration changes were included in the new release.
Could you please investigate why the image-building stage is failing without producing an actionable error? Is this related to Railway's current infrastructure recovery or builder environment?
I'd appreciate guidance on the safest way to complete the deployment while preserving the existing working service.
Thank you.
1 Reply
Status changed to Awaiting Railway Response Railway • 22 days ago
22 days ago
This is on our side. There is an active incident on our build infrastructure (https://status.railway.com/incident/ILLVW9WG, "Builds failing in US West"): builds are failing before any of your build steps run, with the build daemon connection dropping or the build machine never coming up, which is exactly what your deployments show. Your source, build configuration and dependencies are not at fault, and nothing needs to change on your end.
Running services are not affected. A fresh deployment of the same commit may get through in the meantime; otherwise please follow the status page for the all-clear, and redeploy once it is posted.
Status changed to Awaiting User Response Railway • 22 days ago
3 days 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 • 3 days ago