an hour ago
There is some problem with my Railway service deployments that have been stuck in the building of the image phase for an unreasonably long time.
Service: web
Environment: production
Current deployment is okay and running, but all GitHub-triggered deployments after that are stuck at:
Build > Building the image...
for more than 20 minutes without moving on to Deploy, Network, or Post-deploy steps.
There seem to be multiple deployments like that, and no application runtime issues since the image has not been deployed yet.
Previous deployment was fine and these deployments are just usual commits to the service/repository.
Is there any problem with Railway build-worker or queue in this case?
Let me know if you need any deployment/build IDs or logs.
1 Replies
an hour ago
Both of the in-progress builds for your web service were assigned to a build machine about 25 minutes ago and have produced no build output since, so they stopped before any step of your build actually ran. That means nothing in your commits or Dockerfile has been reached yet.
Neither build is waiting in a queue: your workspace is using 2 of its 3 build slots, and both slots are held by these two stalled builds. You can cancel them from the service's deployments list, which frees the slots.
Status changed to Awaiting User Response Railway • about 1 hour ago
Status changed to Solved hacksavvy • about 1 hour ago