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

• 🧵 Unable to Increase N8N_WORKER_CONCURRENCY Above Default of 10 on Railway Deployment
• 🧵 Is there a concurrent connection limit for Railway services?
• 🧵 How to set usage limit?

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

On the Hobby plan, the number of builds you can have at the same time is limited to 3. Were you building 3+ projects simultaneously?

It was on other account with a pro plan. In different projects with +20 services, I made a redeploy of all those projects and the previous error happened again.

On the Pro plan, the number of builds you can have at the same time is limited to 10. Were you building 10+ services simultaneously?

Certanly, the strange thing is that before, when I went over the limit, the extra builds were just put in the queue and executed afterwards without any problem. But now, every time I try to redeploy and keep getting the same error

They get queued up to a bit but once you hit a certain threshold they will just outright fail

We already fixed it. My suspicion is that we accepted two PRs simultaneously in GitHub, and it only pulled the second one, which caused the redeploy to always fail.

Switched branches let us redeploy.