Deployments stuck in queue — Resume-Master service not building
ignotus-21
FREEOP

a month ago

My Resume-Master service has two consecutive deployments stuck indefinitely in QUEUED status:

Affected Deployments:

37c67bb5-5cd2-4bd1-9eee-c16f52a2ecb8 (queued since 2026-07-22 18:19:56 UTC)

a6b3fb8d-a7e1-411a-93dc-64f49e9243e3 (queued after manual redeploy attempt)

Context:

Commit is resolved on GitHub with no errors

Service config is valid: Hobby plan, 1 of 5 services used

No build or deploy errors reported by the platform

Attempted manual redeploy — second deployment also queued immediately

GitHub changes are clean (PR #51 merged successfully)

Project Details:

Project: lovely-vitality (ID: 26e96c48-edea-4b68-a6c9-d044fde73afb)

Environment: production (ID: 84582052-97db-4489-95cb-e26f980fee59)

Service: Resume-Master (ID: c07adf2a-906b-44ef-bed1-a9c4e703f5b4)

Repo: Ignotus-21/Resume-Master (branch: main)

This appears to be a platform-side builder queue issue rather than a service configuration problem.

Solved

7 Replies

Railway
BOT

a month ago

Your deployments are hitting a transient build queue delay that affects all plans. We'd recommend canceling the duplicate queued deployment, since additional redeploys while builds are queued can compound the wait.


Status changed to Awaiting User Response Railway 30 days ago


Railway

Your deployments are hitting a transient build queue delay that affects all plans. We'd recommend canceling the duplicate queued deployment, since additional redeploys while builds are queued can compound the wait.

ignotus-21
FREEOP

a month ago

i tried removing and manually redploying but still goes into the queue


Status changed to Awaiting Railway Response Railway 30 days ago


Railway
BOT

a month ago

The build queue delay is still in effect, so new deployments will also land in the queue. Your existing deployment is still live and serving traffic, so the service itself is not down. We'd recommend holding off on further redeploy attempts for now, as each one adds to the queue, and your queued deployment will proceed once the backlog clears.


Status changed to Awaiting User Response Railway 30 days ago


Railway

The build queue delay is still in effect, so new deployments will also land in the queue. Your existing deployment is still live and serving traffic, so the service itself is not down. We'd recommend holding off on further redeploy attempts for now, as each one adds to the queue, and your queued deployment will proceed once the backlog clears.

ignotus-21
FREEOP

a month ago

same problem


Status changed to Awaiting Railway Response Railway 30 days ago


Railway
BOT

a month ago

The build queue delay is still ongoing and affects all plans. Your current live deployment continues to serve traffic normally. There is no user-side action that will bypass the queue right now, so further redeploy attempts will land in the same state. Your queued deployment will proceed automatically once the backlog clears.


Status changed to Awaiting User Response Railway 30 days ago


Railway

The build queue delay is still ongoing and affects all plans. Your current live deployment continues to serve traffic normally. There is no user-side action that will bypass the queue right now, so further redeploy attempts will land in the same state. Your queued deployment will proceed automatically once the backlog clears.

ignotus-21
FREEOP

a month ago

when will that happen

how much time , i even deleted the backlog deployment but still in queue


Status changed to Awaiting Railway Response Railway 30 days ago


Railway
BOT

a month ago

We don't have a specific ETA for when the build queue backlog will clear. Deleting a queued deployment and redeploying just creates a new queue entry, which is why each attempt lands in the same state. Your latest queued deployment will start building automatically once capacity frees up, with no action needed on your end.


Status changed to Awaiting User Response Railway 30 days ago


Railway
BOT

23 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 23 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...