Skip to content

Runners not allocating

Most runs move from queued to running within seconds. When a run sits in queued or allocating for minutes, one of a few causes is almost always responsible.

Visit the Maxoperf status page first. If there is an active incident affecting allocation in your region, the page will say so along with an ETA.

The most common reason for a run stuck in queued is a plan limit:

  • Concurrent run limit — your plan allows a maximum number of runs at the same time, and you have already reached it. Wait for an active run to finish, or upgrade.
  • Virtual-user limit — the run requested more virtual users than your plan allows. The run will fail to allocate.
  • Capability gate — the run uses a capability your current plan does not include (for example, private locations).

The run page surfaces these limits with a banner that links to the plan-switch flow — see Upgrade or cancel your plan.

If the run uses a managed location:

  • A regional capacity bottleneck can briefly delay allocation. The run will continue to allocate as capacity becomes available.
  • If you need the run to start immediately, retry in a different region.

If the run uses a private location:

  • Open the Private datacenters tab in the workspace.
  • Confirm the agent is running and was online when the run was started.
  • If the agent is offline, restart it on the host. The run will continue to allocate once the agent reconnects.
  • See Connect a private datacenter.

A run with an unusually high runner count can take longer to allocate even on healthy capacity. Start with the smallest runner count that meets your needs and scale up as the test stabilizes.

If a run has been stuck for several minutes and the status page is green:

  • Cancel the run from the run page.
  • Wait a few seconds.
  • Start a fresh run from the same test.

A fresh attempt often succeeds because Maxoperf re-evaluates capacity from scratch.

If you have walked the list and the run is still stuck:

  • Capture the run ID from the URL.
  • Note the region or private location and the runner count.
  • Send those details to support via the Support page.