Run and host
Platform queue and capacity
Platform starts a run when your organization has a free lane. If every lane is busy, Platform saves the run in a queue until capacity opens.
Why a run says queued
Lanes
A lane is one normal slot for an active run, and it remains occupied until that run reaches finished.
Queue
When every lane is busy, Platform saves later submissions in the organization's queue. It considers the earliest queued run first.
Boosts
An owner or admin may apply one Boost to a selected queued run, which can start above the normal lane limit when Platform has technical capacity. Each Boost uses one from the organization's balance; buy more under Settings, Billing. A Boost does not promise an immediate start.
What queueing changes
Queueing only delays the handoff to the controller; Platform does not rewrite the workflow (GraphSpec), node setup (RuntimePlan), input, or declared connection fields. OECP begins later at admitted, so the protocol has no queued state.
How Platform chooses the next run
Normal limit | Each available lane can hold one active run. |
|---|---|
Queue order | Platform uses first in, first out within one organization. |
Freeing a lane | A lane opens only after its current run reaches finished. |
Using a Boost | One Boost applies to one queued run that the user selects. |
Who can use one | Only an organization owner or admin can apply a Boost. |
Boost balance | Platform refuses a Boost when the organization has none left. |
Capacity check | Platform still needs technical capacity before a Boosted run can start. |
If a run remains queued, wait for a lane to open or ask an owner or admin to apply a Boost. A Boost doesn't promise an immediate start when Platform has no technical capacity.