GitHub-triggered deploys hang on Metal builder "unpacking archive"

istiqama-om

HOBBYOP

15 days ago

Every GitHub-push/merge-triggered deployment hangs for ~20 minutes and then FAILS without

ever starting the build. The build log only ever shows:

scheduling build on Metal builder ""

uploading snapshot

unpacking archive (repeated ~every 30s)

…then it reschedules onto a different Metal builder and repeats, cycling across multiple

builders (builder-hwhbgr, builder-cajsxu, builder-debrnq, production-builderv3-us-west1-qb2d),

and finally fails. It NEVER reaches the Railpack banner, dependency install, or build command,

and NEVER emits a "fetched snapshot (X MB)" line. The stall is entirely in source-snapshot

ingestion/unpack, before the builder runs.

This affects every GitHub-connected service in the project (sites, marketing, saas, docs).

CONTRAST — CLI deploys of the SAME repo content succeed in ~2 min:

A railway up deploy fetches a ~1.1 MB snapshot, unpacks instantly, runs Railpack

(pnpm install → next build) and pushes an image.

Solved

3 Replies

Status changed to Awaiting Railway Response Railway • 15 days ago

mykal

EMPLOYEE

14 days ago

We're aware of these transient build queue issues and are actively working on improvements. In the meantime, you can cancel any queued or stuck GitHub-triggered builds to avoid compounding the queue, and use CLI deploys as a workaround until the builder infrastructure stabilizes.

1

Status changed to Awaiting User Response Railway • 14 days ago

mykal

We're aware of these transient build queue issues and are actively working on improvements. In the meantime, you can cancel any queued or stuck GitHub-triggered builds to avoid compounding the queue, and use CLI deploys as a workaround until the builder infrastructure stabilizes.

istiqama-om

HOBBYOP

14 days ago

thanks @mykal .. I was wondering if I am doing something wrong for couple of hours

Status changed to Awaiting Railway Response Railway • 14 days ago

Status changed to Solved Railway • 14 days ago

mykal

We're aware of these transient build queue issues and are actively working on improvements. In the meantime, you can cancel any queued or stuck GitHub-triggered builds to avoid compounding the queue, and use CLI deploys as a workaround until the builder infrastructure stabilizes.

istiqama-om

HOBBYOP

14 days ago

I suggest to have status bar to inform users if there is any issue related to what they are doing (if build stuck, user can be informed that its an issue and being fixed)