24 days ago
Project: content-quietude
Project ID: 87f17c58-3a33-47f9-abc3-c916f9bd6cee
Service: ethflow-pf-connector
Service ID: 8adce3fa-23da-4f29-9595-d3ac29b0a80e
Repo: pitalenkopl-web/ethflow-pf-connector (private), branch main
Builder: Railpack (default)
Symptom: every deployment gets stuck at "scheduling build" with zero further log output. After about 5 minutes Railway reassigns to a second builder, which also produces no output. The build never reaches npm install or any actual build step. This happened across three different regions, and repeated in the same region (EU West) again after waiting about 1 hour, hitting the exact same two builder instances both times.
Evidence (deployment ID, region, builder 1, time, builder 2, time):
2ce92bd0-cbb7-4704-a190-099036790383, US West, builder-xdnrix 14:33:06, builder-oxfzpt 14:37:54
30e94f06-0714-40bf-908b-8583155b298f, US East, builder-lbhkbs 15:06:12, builder-erzvyw 15:10:56
c2f492c4-dfbc-4744-a7df-ca4359949df4, EU West, builder-bfsxmt 15:18:03, builder-zjatre 15:22:51
4c9d9d2f-9af5-4550-b348-59e93e0cba3e, EU West retry +1h, builder-bfsxmt 16:09:30, builder-zjatre 16:14:25 (same two builder instances as the attempt an hour earlier)
What I've tried: switching regions (US West to US East to EU West), waiting about 1 hour and retrying, aborting and redeploying via fresh commits. All deployments manually aborted after confirming the pattern; no active or hanging deployments remain.
Account is currently on the trial plan (30 days or $5.00 left shown in UI) - flagging in case build scheduling priority is relevant.
I see several similar threads already reported (stuck at "waiting for build to start", "QUEUED" builds, "no output on Metal builder", "zero active builds") so this looks like a known recurring issue rather than something isolated to this project. Would appreciate confirmation either way, and any update on root cause.
1 Replies
Status changed to Awaiting Railway Response Railway • 24 days ago
24 days ago
Your repo has a directory whose name is the text of a package.json file, several hundred characters long. That's past the filename limit on the builder's filesystem, so unpacking your code archive fails before any build step runs, which is why you get no output.
It followed you across regions because every builder receives the same archive and rejects it the same way. The trial plan isn't involved.
Find it with:
git ls-files | tr '/' '\n' | awk 'length($0)>255'Rename or delete what that prints and push. It looks like a shell command wrote the JSON into the filename instead of into the file.
We're fixing the error message too. A generic build failure pointing at an empty log is what made this look like an outage on our side.
Status changed to Awaiting User Response Railway • 24 days ago
16 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 • 16 days ago