Each Nx Cloud organization has a limit on how many workers can run at the same time, shared by every run in every workspace of the organization. When your organization is at the limit, new runs wait in a queue until enough workers free up.
The limit
Section titled “The limit”| Plan | Concurrent workers |
|---|---|
| Hobby | 25 |
| Team, CI team | 25, or with a worker pack 50 ($75 a month), 75 ($150), or 100 ($225) |
| Enterprise | Set by your contract |
The pool counts every worker Nx Cloud runs for your organization. A main-job worker doesn't count, and neither do machines you run yourself through bring your own compute.
A run gets all of its workers at once: one that asks for 20 waits until 20 are free. A run that asks for more than the limit gets the limit.
How queueing works
Section titled “How queueing works”A queued run's page in Nx Cloud shows how many tasks are waiting for workers. Queued runs start in the order they arrived.
A queued run is cancelled when a new push lands on its branch, or once it has waited an hour.
If runs queue often, raise the limit or give small changes fewer workers with distribute-on changesets.
Raise or lower the limit
Section titled “Raise or lower the limit”On Team and CI team, set the limit in your organization settings. A higher limit applies as soon as it's set and is prorated for the rest of the month. A lower limit takes effect at the end of the calendar month, and never stops workers that are already running.
On Hobby, switch to Team or CI team to raise it (compare plans).
On Enterprise, the limit is part of your contract. Talk to sales to change it.
See current usage
Section titled “See current usage”Your organization's usage page in Nx Cloud has a Concurrent workers card with the limit, the workers in use right now and how many are waiting in the queue. The billing page lists the limit with the rest of your plan, and a queued run's page shows the in-use count and the limit.