Bamboo deployment environment "no agent" in CI

Deployment environments match against agent capabilities just like build jobs. When no online agent satisfies the environment's requirements, the deployment queues with "no agent" and the release stalls.

What this error means

A deployment sits in "Queued" and the environment shows it cannot start because no capable agent is available, even though build agents are online.

Deployment queued: no agent is available to execute this environment.
The environment requires a capability that no online agent provides.

Common causes

The environment requires a capability build agents lack

Deployment tasks (deploy scripts, SSH, cloud CLIs) demand a capability that only build-focused agents were given, so the deployment finds no agent.

Deployment-capable agents are offline or dedicated elsewhere

Agents tagged for deployment are disabled, offline, or reserved for other environments, leaving none available.

How to fix it

Give a deployment agent the required capability

1. Open the deployment environment and read its requirements.
2. Add the matching capability (executable, custom key) to an online agent, or dedicate an agent to deployments.
3. Re-trigger the deployment.

# Deploy > <project> > <environment> > Agents / Requirements
# Agents > <agent> > Capabilities > add the executable or custom key the environment needs

Bring deployment agents online

Enable or restart the agents intended for deployments so the environment has capacity to run.

How to prevent it

• Keep at least one online agent capable of every deployment environment.
• Define deployment tool capabilities as shared keys so agents stay consistent.
• Monitor deployment queue times separately from build queue times.

Related guides