Bamboo "No agents are available ... capabilities" in CI

Bamboo matches a job's requirements against each agent's capabilities and found no online agent that satisfies all of them. The job sits in the build queue with "no agents are available" instead of running.

What this error means

The job stays queued and the queue view shows "There are no agents available that can build this job" or "No agents are available which can run this build". The build never starts.

There are no agents available that can build this job.
This build has been queued for 14 minutes.
The build cannot be started because no agent can satisfy its requirements.

Common causes

A job requirement has no matching agent capability

The job demands a capability (a JDK label, an executable, a custom key) that no online agent defines, so the requirement/capability match produces zero eligible agents.

The only capable agents are offline or busy

Agents that would match are disabled, offline, or fully occupied, leaving no available agent to pick up the job.

How to fix it

Compare the job requirements to agent capabilities

1. Open the job configuration and read its Requirements tab.
2. In Agents, open an agent and check its Capabilities for each required key.
3. Add the missing capability to a dedicated agent, or relax the requirement if it is not truly needed.

# In Bamboo administration:
# Agents > <agent> > Capabilities > Add capability
# match the exact key the job Requirements tab lists (e.g. system.jdk.JDK 17)

Bring a capable agent online

If a matching agent exists but is offline or disabled, restart the remote agent or enable it so Bamboo can schedule the job.

How to prevent it

• Keep at least one agent per required capability set, not a single overloaded agent.
• Use shared capabilities so a JDK or tool key is defined consistently across agents.
• Alert on jobs queued longer than a threshold to catch capability gaps early.

Related guides