Build queue

Your plan runs a fixed number of builds at the same time, across the whole workspace. A build started when every slot is busy isn't refused: it waits in a queue.

How the queue works

• Queued builds start oldest first, as soon as a slot frees up.

• The deployment's status is Queued until then, with its position in the queue, in the dashboard and in the CLI:

  ⏳ Queued · position 2 · 0:42 — waiting for a free build slot

• When the queue itself is full, a new build is refused with HTTP 402 and a message naming the limit.

Waiting for a build machine

A build can also wait while your plan has a free slot: when every build machine is busy across Hiraiship. It stays in the same queue, and says so:

⏳ Queued · position 1 · 0:12 — waiting for a free build machine

It starts as soon as a machine frees up, in the order it was queued. Paid plans have machines that Free builds never use, so a burst of Free builds doesn't hold up a paying workspace's builds. Enterprise and Platform have their own on top.

The API tells the two cases apart with the deployment's queueReason: plan_limit when your plan's builds are all running, capacity when no machine is free.

Canceling a queued build

A build can be canceled while it's queued: open the deployment and choose Cancel build. It's marked Failed, with "canceled" as the reason. A build that already started can't be stopped; it runs to the end or to its timeout.

Ctrl-C in the CLI doesn't cancel anything: the build stays queued and starts when a slot frees up.