Repeated production deployment failures on Railway builder-ldhvbe
macroer16
FREEOP

24 days ago

Hello Railway Support,

I am experiencing a repeated production deployment failure for my SANDS service.

Builder:

builder-ldhvbe

There have now been 9 deployment attempts with the same behaviour:

  • Build is scheduled on Metal builder "builder-ldhvbe"
  • Immediate failure
  • Zero further build output
  • Failure occurs before application/dependency build commands run

Railway's dashboard classifies this as an INFRASTRUCTURE ERROR.

The same commit/configuration previously built successfully, and the existing production deployment remains healthy:

Production deployment:

5c462c63

Health endpoint:

/health = OK

The application has also been independently verified locally:

  • Fresh-process import verification passed
  • py_compile passed
  • Relevant regression tests passed
  • 498-test regression suite was previously green

Failed deployment IDs include:

bc564185

919113a1

132573f4

All failed with the same builder/signature.

Railway's own diagnostic indicates this is likely related to the builder/build execution environment rather than the application code.

Could you please investigate builder-ldhvbe and reassign/repair the builder if necessary so deployment can resume?

The current production deployment is healthy and there is no production outage.

Thank you.

Solved

1 Replies

Railway
BOT

24 days ago

The build logs show that Railpack is scanning the repository root and finding only subdirectories (backend/, frontend/, sands-website/) with no buildable entry point at the top level, so it exits with "Railpack could not determine how to build the app." Your SANDS service has no root directory configured, so every deploy attempts to build from / where there is no application code. To fix this, open the SANDS service, go to the Settings tab, and set the Root Directory to the subdirectory that contains the application you want to deploy (e.g. /backend), then redeploy.


Status changed to Awaiting User Response Railway • 24 days ago


Railway
BOT

17 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 • 17 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...