a month ago
My service deployments are stuck in a QUEUED state and are not being picked up for processing, even though the service itself reports healthy and there are no GitHub/branch/config issues on my end.
Project ID: 515df5b0-0dc5-446a-8f89-45caa1a034df
Service ID: 552580cf-3f78-459e-bca7-0d9077690cb3
Environment ID: c747050a-e8e6-48b9-b94d-a36385f58cf5
Repo: ozodbekernazarov6642/TDIU-Olim-fondi, branch: main
Stuck deployment IDs:
932e194d-511b-42c6-87c5-2dfe8139f8b2
3bb55658-a740-4939-b332-af82b2af108e
6b4320ef-909e-478c-bd33-58a8782a12b1
Already confirmed: GitHub status and Railway status both show fully operational. Branch is correctly connected to main. Manually triggered a fresh deployment of main HEAD but it also queued instead of building.
Could someone from the team manually release the queue or check why new deployments aren't being picked up for processing?
1 Replies
a month ago
Your deployments are stuck in QUEUED because your workspace subscription is currently inactive, which prevents new builds from being picked up. You can resolve this by visiting your workspace billing page to activate your Hobby plan subscription.
Status changed to Awaiting User Response Railway • about 1 month ago
24 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 • 24 days ago