Hey there! We've found the following might help you get unblocked faster:

• 🧵 Deployments stuck in "Queued. Waiting for deployment slot"

• 🧵 Deployments stuck in "Queued. Waiting for deployment slot"

• 🧵 Deployment got stuck and now waiting for build slot

If you find the answer from one of these, please let us know by solving the thread!

None of these seem to apply. Please consider escalating this. I have tried troubleshooting it for hours and I literally cannot accomplish anything work wise until its resolved.

If you have tons of services tied to a single repo, this is 100% going to happen. If you need more build slots you're welcome to reach out about enterprise and we can chat there. That'll likely start at about $1000/mo

Okay. that makes sense but I guess I would've expected it to have already happen (I don't think I've added a service in a week at least), and I don't fully understand why I'm just purely "stuck" at this point. Surely there must be some way I could sacrifice or regulate deployment triggers so that I could just build one at a time if I wanted to fix the situation internally?

Basically, I'm just wondering why it happened today instead of any of the other times since I've had the same number of services for a week or more. I'm very, very concerned with my options for fixing it.

Am I just way overreaching my pro plan? I have no idea what you mean by "tons" (no offense whatsoever, I've actually been interested in an enterprise plan potentially) I think railway is elegant and incredible. I am attaching a screenshot of my "backend project" services. I have two more on my "frontend project". Is this tons? I genuinely have no idea. I have no true formal background in software development and railway is my first company that I've ever used as a PAAS or whatever you would call my implementation.

You mentioned explicitly "tied to a single repo". Is that part of the problem? Does that somehow amplify the problem? Would putting them on separate branches temporarily fix the problem? I don't need to redeploy all of my services anymore on every single push. Originally it was just a nicety, back when I only had about 3 services. For example, I was extremely close to merging my most recent branch and then setting 90% of my services to not deploy on every push.

Again, I really have no context for what I should be expecting, and I'm sorry if my naivety comes off as annoying. I'm earnestly interested in keeping railway and happy to work fairly with the business I do inside railway.

I have no idea what "costs" Railway more money for doing business or how I can be a good customer that isn't trying to unfairly advantage myself against you.

My concern is just that I haven't seemed to be able to fix the problem even when I tried to do a single new deploy for a single service. Again, is that just where I'm at with my limitations? Or am I missing something obvious about the solution?

Is deploying constantly very expensive for Railway? Is that the problem?

I'm truly a novice and I really appreciate you getting in touch with me.

Happy to reach out to enterprise solutions if that is my only course forward. At the moment I just really wanted to at least get things functional so I could test out the latest applications I'd been working on.

PS. I didn't mean to break the rule about posting a copy on discord. When I looked at the discord thread, mine didn't show up in the history so I mistakenly thought they were somehow separate (even though that seemed weird). I am in no way trying to "game the system". I'm just very new to software development, and very new to Railway.

According to this I hadn't even come close to maxing out my usages, so I thought it must not be an issue. If that's deceiving relative to the issue of "tons of services", and not enough build slots, then I accept that.

Oh, thanks by the way. I guess I made it through the queue. I didn't realize it might be like a global queue (I was thinking it meant relative to just my account for some reason). I see that my deploys that I'd been waiting on did make it through now.

Again, I'm mostly interested in understanding what is occurring and what I will need to do from here. I will do more research in the meantime.

I had been following this same method/pattern for a few weeks now in general, so I just hadn't thought anything of it.

I didn't realize it might be like a global queue (I was thinking it meant relative to just my account for some reason). I see that my deploys that I'd been waiting on did make it through now.

There's a global queue and also a per-account queue; upgrading will bump your per-account limits.

You deployed during a peak period where our build/deploy queue had a tiny bit of hiccup, but this shouldn't happen again if you're deploying a reasonable number of times