You'll need to check each service - to do this, open your Railway project and click each service one by one, go to the Deployments tab and look for deployments that have the statuses Building, Queued or Pending. These are what will be consuming your concurrent build slots.

If any of them are stuck and taking up slots, open the deployment, and click Cancel/Stop build, repeat this for all your other services until the builds are cleared. Once enough of them are stopped or finished, new deployments will work again.

Hope this helps!

This could be happening for many reasons.

Go to the Settings of your Workspace (not the project) to view active usage. If nothing is building visually but you still get the error, toggle the "Root Directory" setting in your service to ./ and back again to force a reset of the build trigger logic.

Do you have another project entirely (unrelated to Aurelia) that is currently building?

Are you part of a Team Workspace? If a teammate is deploying their project at the same time you are, you share the same build limit.

(Most likely) You have to wait for the other project to finish, or upgrade the workspace plan to allow multiple concurrent builds (Pro plan usually allows more).

But first make sure of these things:

Go to your Service Settings in Railway.

Find "Watch Paths".

Tell Service A to only build when files in /server change.

Tell Service B to only build when files in /client change.

I hope this helps you! Happy holidays.