Summary
Our Railway service is stuck during deploy at the “Creating containers…” stage. The build completes successfully every time, but the container never starts. There are no deploy logs, no runtime logs, and no healthcheck activity. This same code and configuration were deploying successfully until today with no breaking changes.

Key details

• Build phase completes successfully (Nixpacks finishes, image is built and pushed)

• Deployment phase never progresses past “Creating containers…”

• Deploy Logs tab is empty

• App never executes (no startup logs)

• Healthcheck never runs

• Redeploying does not help

What we have already tried

• Redeploying multiple times

• Pushing new commits

• Adding new environment variables to force cache invalidation

• Verifying app listens on process.env.PORT and 0.0.0.0

• Confirmed this is the exact same code/config that deployed successfully before

What we believe is happening
This appears to be an infrastructure-level issue where the container scheduler for this service/region is failing to start containers. The image builds and pushes correctly, but the container never transitions to a running state, resulting in no logs.

Impact

• This is a production Shopify app

• The app is using the default *.up.railway.app URL (no custom domain), so duplicating or recreating the service would break existing installs

• We are blocked from deploying fixes

Request
Can you please:

• Investigate whether the service or region scheduler is wedged

• Reset or reassign the container slot for this service

• Or advise on a safe recovery path that does not change the public URL