Project: editorialhub-preprod (id 0f2736ed-30a1-4004-8926-e5cf5c678a94)

Service: editorialhub (id 5ddc2f47-b0a9-4eea-8356-62d72361d9b1)

Environment: production

Issue: deployments fail at "Create container" step. Build completes 100% successfully — image is built and pushed to registry — but the orchestrator never starts container creation. Result: "Failed to create deployment" without specific error message.

Build logs of failed deployment 5a3c3f32 confirm:

- npm ci OK

- nest build OK

- exporting to docker image format OK

- containerimage.digest: sha256:1faa2219d099f289a1b74813f1b2dde4d76d6be3c349aafe214ebea168901f3d

- image push OK (last log entry at 2026-05-05 20:54:17 UTC)

- After image push: nothing. No "Create container" step initiated.

This pattern repeats across ALL recent deploys (multiple commits, multiple empty commits, post-restart attempts):

- 4ca810c3-05ee-48cb-8677-e28cc3852906 (initial F1.2 push, commit 5d448f5)

- Subsequent CLI redeploy of same commit

- Empty commit daf6d4f

- Empty commit 035c266 (post-restart of active deployment)

Currently active deployment serving traffic: commit d288564 (deploy id from 2026-05-05 19:09 UTC), status SUCCESS, RUNNING. The active service works correctly. Only NEW deploys fail to create containers.

Manual actions taken (none destabilized the issue):

- Restart of active deployment via dashboard: completed successfully

- Manual cancellation of stuck deploys via dashboard

- Multiple push attempts including empty commits

Service configuration:

- Source: AdminEdHub/editorialhub, branch master, rootDirectory /backend

- Builder: Railpack V3

- Mounted volume: editorialhub-volume (id 27d590b5-268f-4107-aa4f-52a3d3019e28) at /app/uploads with production data

- Region: us-west2, 1 replica

- 25 custom env vars including DATABASE_URL referencing the project's Postgres service

Postgres service in same project deploys and runs fine — issue isolated to "editorialhub" service.

Note: I see at least one similar thread from 9 days ago ("Deployment fails at 'Create container' step — 'Failed to create deployment'") still without official Railway response. If this is a known recurring infrastructure issue, please advise.

What I need:

Orchestrator-side investigation. Image is built and pushed successfully but container creation is never initiated for this specific service.

Thanks.