an hour ago
This appears similar to the existing “scheduling build on Metal builder” reports, but this is a current reproducible incident affecting three consecutive staging deployments on builder builder-fstdwd.
Railway project fortunate-charm, environment staging, service google-maps-calls cannot schedule builds on Metal builder builder-fstdwd.
Three deployments from the same unchanged candidate failed before source checkout or build execution:
- 589cba1e-1478-4209-8dfb-3361c689b228 — 2026-09-15 06:49:33Z
- f09529e0-b489-447b-ab60-efd5c6fa51e6 — 2026-09-15 06:51:46Z
- 619a2a02-9a93-4a74-adec-302430b1f46a — 2026-09-15 07:07:06Z
All three stop at:
scheduling build on Metal builder "builder-fstdwd"
No repository checkout, Railpack/Docker build, npm install, application build, migration or startup output appears.
Source candidate:
d96ba91b731ab2292fe484e4bb82c6292c84ead3
Configuration remained unchanged:
- root: backend
- runtime: V2
- builder: RAILPACK
- no custom build/start command
The previous successful deployment bde06395-a8dd-46d8-8124-3ed91c9def6f remains active and healthy. /health returns HTTP 200.
Could you please confirm whether builder-fstdwd or the Metal build scheduler for this project/environment is currently unhealthy, and advise whether Railway can reschedule this service onto a healthy builder or if any project-side action is required from us?
We intentionally stopped retrying after three identical failures.
2 Replies
an hour ago
All three deployments failed at the BUILD_IMAGE step in about 2 seconds with the error: Root directory "backend" was not found in the deployed source. The builder is not stuck or unhealthy. The build was rejected before it reached the builder because the backend directory does not exist at the root of the deployed commit on the integration/mapcaller-accepted-baseline branch. Verify that the branch still contains a backend directory at its root, or update the root directory in your service settings to match the repository structure at that commit.
Status changed to Awaiting User Response Railway • about 1 hour ago
Railway
All three deployments failed at the BUILD_IMAGE step in about 2 seconds with the error: `Root directory "backend" was not found in the deployed source`. The builder is not stuck or unhealthy. The build was rejected before it reached the builder because the `backend` directory does not exist at the root of the deployed commit on the `integration/mapcaller-accepted-baseline` branch. Verify that the branch still contains a `backend` directory at its root, or update the root directory in your service settings to match the repository structure at that commit.
33 minutes ago
Thanks. I still need help because the diagnosis appears inconsistent with the actual Git repository state.
I verified the repository directly on GitHub.
The backend/ directory exists at the repository root in BOTH exact commits:
Candidate:
d96ba91b731ab2292fe484e4bb82c6292c84ead3
Canonical:
4aa5fa83574724a67d27b9a670adaeea419dad2c
Therefore Root directory "backend" was not found in the deployed source does not match the actual tree for either SHA.
There is also a second discrepancy:
The failed deployments were intended to deploy the M13 candidate:
feature/m13-legal-registry-acceptance
d96ba91b731ab2292fe484e4bb82c6292c84ead3
but your response says Railway evaluated the source from:
integration/mapcaller-accepted-baseline
Could you please check which exact repository, branch/ref and commit SHA Railway actually resolved for deployment IDs:
- 589cba1e-1478-4209-8dfb-3361c689b228
- f09529e0-b489-447b-ab60-efd5c6fa51e6
- 619a2a02-9a93-4a74-adec-302430b1f46a
Specifically, please confirm:
- repository resolved by Railway;
- branch/ref resolved;
- exact commit SHA resolved;
- repository root contents Railway saw;
- why Railway reports backend/ missing when it exists in both relevant Git trees;
- why the deployment appears to resolve integration/mapcaller-accepted-baseline instead of the intended M13 candidate branch.
At this point this looks like a deployment source/ref resolution issue rather than an application-code or repository-structure issue.
We have stopped further retries until the resolved source/ref is clarified.
Status changed to Awaiting Railway Response Railway • 22 minutes ago