Hi Railway team,

Since June 25, 2026, every deployment in my project fails and I've isolated it to the build step never executing. I'd appreciate help investigating the builder.

Project / environment

Project: kingdom-sports (ID 59173367-0475-4098-9733-749c0eaff80a), environment production, Hobby plan

Affected services: ksp-backend (ID fffd13a2-e0eb-454d-afb6-c70efbf3287f) and ksp-dashboard

Builder shown in logs: builder-kctobv (Metal)

Symptom

Every build's logs contain only:

scheduling build on Metal builder "builder-kctobv"

…and then nothing — no Docker build steps, no image, no healthcheck. The deployment goes straight to FAILED. The previously deployed container (from June 25) keeps serving fine; only new builds fail.

What I've already ruled out (please don't send me back to these)

Not the Dockerfile/config — the last successful deploy (afe90833-ee01-4d08-8987-4b26517bb928, June 25) used the exact same Dockerfile + railway.json, unchanged since.

Not the deploy method — fails identically via GitHub source (e.g. deployment 3d640271-9d9f-420d-a4cd-ff14463950f1) and via railway up CLI (e.g. ab72c167-5716-416a-8756-1764ab656e88, 371bdbd9-..., 02aeb6a6-...). Both die at the same "scheduling build" line.

Not the app — Alembic migrations run cleanly when pointed directly at the prod Postgres; the app boots fine locally and in the old container.

Not GitHub access — the Railway GitHub App is installed on the account with All-repositories access; GitHub auto-deploy now triggers correctly (the build itself is what fails).

Sample failed deployment IDs (ksp-backend)

3d640271-9d9f-420d-a4cd-ff14463950f1, ab72c167-5716-416a-8756-1764ab656e88, 371bdbd9-8ca5-4824-b749-513723773d89, 02aeb6a6-1a43-480c-89d2-b371f22e17aa, 1ba687d3-2ffa-4209-aeb8-56bf34e389ae

Ask: Can you check why builder builder-kctobv is scheduling builds for this project but never executing them (no build output at all) since June 25? Is there a builder/region issue or account-level flag blocking my builds?

Thanks,

Greg