4 hours ago
Our production Next.js service omia-website has failed to build the same GitHub commit twice. Both builds stop during Build image, before any npm install or npm run build output. The previous deployment remains active, so we cannot publish an urgent storefront change.
Project: alluring-amazement (49b25dd7-f5b7-4653-859e-de4855fff557)
Environment: production (99d0d34d-1d6a-4429-971f-5b83c78ab294)
Service: omia-website (d9d44757-b87a-4fed-aedc-c5647aec7181), region US East, 1 replica
Commit: 86644c6, “Pause online shop checkout and payment links”
Failed deployments: e9be93d2-7da0-4656-a637-211d5c278360 and def234cd-c2ac-494b-a956-d137e398c893 (redeploy of the same commit)
Build driver: railpack-v0.43.0, Node 24.22.0; npm detected from package-lock.json.
Final error in both build logs: Build Failed: build daemon returned an error < failed to run Build function: frontend grpc server closed unexpectedly >
Local npm run typecheck and npm run build both pass. There is no application build error in Railway logs; the failure occurs before npm starts.
Could you investigate the build daemon for these deployment IDs and advise how to get this production commit deployed? We already retried the failed deployment once without success. Please let us know if a fresh Deploy Latest Commit is now expected to work or if the builder needs intervention.
2 Replies
4 hours ago
Both builds got through snapshot upload and Railpack's build plan (Node 24.22.0, npm install, npm run build), then failed while the builder was starting Railpack's build frontend, before any step ran. The full error was "build daemon returned an error: failed to run Build function: frontend grpc server closed unexpectedly". So the failure happened before your code or dependencies were touched, which matches what you saw locally.
We haven't found what caused it. We also can't promise a new attempt will work. The cleanest next step is a fresh Deploy Latest Commit (or an empty commit pushed to trigger one) instead of Redeploy on a failed deployment. Your current deployment keeps serving traffic while it builds.
If that build fails the same way, please share its deployment ID and the time it failed in UTC, so we can compare it with the two failures from 16:01 and 16:13 UTC today.
Status changed to Awaiting User Response Railway • about 4 hours ago
an hour ago
Update: a fresh Deploy Latest Commit succeeded. Deployment c52814fd-ac5d-4103-a113-a2bdcf724784 built and activated commit 86644c6. We verified the live storefront: checkout is disabled as intended. Thank you for the guidance.
Status changed to Awaiting Railway Response Railway • about 1 hour ago
Status changed to Solved Railway • about 1 hour ago