Skip to main content

Deploy Agent Swarm

Triggered when an agent swarm package is deployed or redeployed through the Deploy action. It is the agent swarm counterpart of Deploy Application. On top of rolling out the agents, it also connects them to the account's Agent Gateway.

Deploy Agent Swarm job detail

The header shows the Agent Swarm and its package version, along with who Requested the deployment and when. Each target environment is listed with its own Status and expands to the phases of the rollout:

  • Configuration check — validates the deployment configuration, including each agent's service account
  • Quality gates / Extended quality gates — evaluated only if continuous delivery quality gates are configured for the environment
  • Deployment — applies the package to the environment and waits for the agents to become ready
  • Agent gateway provisioning — registers the exposed agents in the Agent Gateway and sets up their A2A connections and access

A phase can finish with a warning without failing the job — for example when the rollout waits on missing secrets, or when some agents could not be registered in the Agent Gateway. Check the phase detail for the affected agents.

Things to know​

  • Deployment and Agent gateway provisioning cannot be cancelled once they have started; earlier phases can.
  • Deployments and undeployments of the same agent swarm in the same environment never run in parallel — a newer job waits until the previous one finishes, in the order they were requested.
  • A job that waits too long (24 hours) is cancelled automatically, unless it is in a phase that cannot be cancelled.
  • A failed job can be retried, either as a whole or for a single environment.