ersistent builder pool failure — deployments stuck scheduling across Metal builders
vili651
HOBBYOP

a month ago

I'm experiencing a persistent infrastructure issue with my Lora-Claude service where deployments fail to build across multiple retry attempts.

Failed Deployments:

  • 4643fea0-a62d-48ec-bc83-599d6e45e386 (2026-07-16 22:58:18Z)
  • 6d3781a2-bcb6-4d87-8e0a-d3c72bb47e8f (retry, stuck)
  • b41bc6ef-130e-46a1-be78-5c00f8b0f8f7 (retry 2, stuck)

Issue: Build logs show only scheduling messages with no actual build execution across multiple Metal builders. Zero build output at any stage (no Railpack, no dependencies, no compilation).

Triggering commit: trivial CSS/JSX changes only (17 lines, no dependencies changed). Previous deployment succeeded ~2 hours ago with identical toolchain.

This is clearly a builder infrastructure fault. Need manual intervention or alternative builder routing to deploy.

Solved

1 Replies

Railway
BOT

a month ago

This matches a known pattern of builds getting stuck at scheduling with no build output. Please cancel any stuck deployments and wait before re-deploying, as additional retries can compound the queue.


Status changed to Awaiting User Response Railway about 1 month ago


Status changed to Solved vili651 about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...