Consistent Deploy Failures Without Log Details
desmaraismax
HOBBYOP

2 months ago

Hi Railway Support,

I'm experiencing a critical deployment issue with my backend service where builds are

failing consistently.

Symptoms:

- Railpack successfully prepares the build plan

- Build logs show "Successfully prepared Railpack plan for build"

- But then the actual build commands (npm ci, build step) never execute - zero output

- No error messages, just silent failure after plan preparation

Timeline:

- Last successful deployment: March 14, 2026 ~2:00 AM UTC (commit cfc577d)

- Issue started: All deployments after this commit fail with the same pattern

- Every deployment since then (10+ attempts) shows the same behavior

What I've tried:

- Clearing Root Directory field (blank vs / vs /backend)

- Removing/modifying Build Command

- Deleting and restoring Dockerfile

- Regenerating package-lock.json

- Manual deploys vs auto-deploys

- All produce the same result: plan prepares, then nothing executes

Project details:

- npm workspaces monorepo structure (backend, frontend, shared packages)

- Node.js 20.20.1

- Railpack 0.18.0

- No billing issues, no resource warnings visible in dashboard

Example failed deployment logs:

[inf] ╭─────────────────╮

[inf] │ Railpack 0.18.0 │

[inf] ╰─────────────────╯

[inf] ↳ Detected Node

[inf] ↳ Using npm package manager

[inf] ↳ Found workspace with 2 packages

[inf] Steps

[inf] ──────────

[inf] ▸ install

[inf] $ npm ci

[inf]

[inf] ▸ build

[inf] $ cd backend && npm install && npx playwright install --with-deps chromium &&

npm run build

[inf]

[inf] Successfully prepared Railpack plan for build

[inf]

[inf]

(deployment fails here - no further output)

Is there a known issue with Railpack execution, or has something changed with the

platform? The fact that the exact same commit worked yesterday but nothing works now

suggests a platform-level issue.

Can you help investigate what's blocking the build execution?

Thank you!

Solved

1 Replies

Status changed to Awaiting Railway Response Railway 2 months ago


sam-a
EMPLOYEE

2 months ago

This was a known platform-side issue affecting build execution that we've been tracking. Fixes have since been deployed, and we can see your service is now running successfully. Sorry for the trouble! Let us know if you still have any issues.


Status changed to Awaiting User Response Railway 2 months ago


Status changed to Solved sam-a 2 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...