a month ago
Seeing the same "Failed to build an image" / build failures reported
in 5 other threads here today.
My sequence (April 26 evening):
1. Pushed commit ec1edaa to main → triggered deploy (build ID 78c9b65e).
2. Build succeeded but registry push failed. Diagnose tool said:
"Image built successfully four times across four different build
servers, but deployment failed when publishing the image to
Railway's container registry. The code changes in this commit
are unrelated to the failure."
3. Triggered redeploy (build ID ddae1675) → currently 10+ minutes
in "Queued" status, not actively building.
Status page shows fully operational, but Deployments uptime is at
99.91% with visible recent incidents.
Not urgent — previous deploy is still serving traffic. Just need
the queue to clear so commit ec1edaa can ship. Happy to wait if
infra team is already on it.
Thanks!
1 Replies
a month ago
Your redeploy appears to have cleared the queue and is now active. The runtime logs from that deployment show it processing requests successfully (price scans completing with no errors). The initial registry push failure on the first build was a platform-side issue, not related to your code. If the service still shows as "BUILDING" in the dashboard but is clearly running, you can safely treat it as deployed.
Status changed to Awaiting User Response Railway • 26 days ago
19 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 • 19 days ago