This wasn't anything in your service or your plan limits. Around the time your deploy failed, our scheduler briefly ran short on capacity to place new containers, which is what threw that error. That's cleared up since. Give it another deploy and it should go through. If it fails again, reply here and we'll dig in.

Railway Team

I have got the same issue right now

Can I have a link to the deployment having this issue?

I had and having the same issue for some days now trying again worked but it should be fixed. Link to deployment: 6dc940cb-259b-40cd-8d45-7bd81ca4814b after enabling Railway Express

Your deploys weren't blocked by anything in your service or your plan. Your Backend container is a large one, and with Railway Express we start the new version alongside the old one before switching traffic over, so for a moment a deploy needs room for both to run at once. Around when yours failed, we briefly couldn't find a host with that much free space in your region, which is what threw the "no available stackers" error. That cleared on its own and your later deploy went through, which matches what you saw. If it happens again, retrying a few minutes later is the quickest fix, and just reply here if it keeps recurring and we'll dig in.

In my case, I have never not had the "ScheduleAndBootVM: create instance: no available stackers found within resource limits" error since I created my account. For legal reasons I must deploy within the EU and so far your service has been un-usable because of it. This issue has happened non-stop for me for the last 18 hours with commits on our codebase averaging every hour (and every time the deployment failed)

We are evaluating moving to Railway but so far noting has worked.

Apologies, we misdiagnosed this earlier. It isn't transient capacity, and it isn't your service or plan.

The failures come from Railway Express (the "Try Railway Express" toggle in your service settings). Express currently only runs in our US West region, so with it enabled, deploys to the EU or Asia can't be scheduled, which throws "no available stackers found within resource limits." That's a bug on our end, and we're fixing it so Express falls back to the standard path instead of failing.

To unblock right now: open the service settings and turn off "Try Railway Express." Your deploys will go through the standard path, which works in every region, and you can keep your current build setup.

Your running deployment stays live throughout. Once the fix ships you can re-enable Express in those regions.