A target version pins a deployment to a specific tool bundle version. When you set a target version, all edge connectors in that deployment will download and use that exact version of the tool bundle, regardless of whether newer versions have been published.
This gives you precise control over rollouts. You can test a new bundle version in a staging deployment before promoting it to production, or roll back to a known-good version if issues arise.
Bundle assignments link a specific tool bundle to a deployment. This determines which set of tool implementations edge connectors in that deployment will download and execute.
One bundle per deployment
Each deployment is assigned a single tool bundle at a time. When you change the bundle
assignment, connectors will download the new bundle on their next sync.
Version pinning
Combine bundle assignment with a target version to lock a deployment to a specific snapshot of a
tool bundle.
To assign a bundle:
Open the deployment from Admin > Deployments.
In the Tool Bundle section, select the bundle you want to assign from the list of available bundles.
Optionally set a target version to pin the deployment to a specific version of the selected bundle.
Save the deployment. The assignment takes effect on the next connector sync.
Edge connectors poll the platform for bundle updates on a regular interval:
Default polling interval — every 10 minutes.
When a connector detects that its current bundle version differs from the deployment’s target version (or the latest version, if no target is pinned), it downloads the updated bundle automatically.
The download is atomic: the new bundle is fully downloaded and validated before replacing the previous version. Tool calls in progress continue using the old bundle until they complete.
You can set a default bundle for your organization. When a new deployment is created without an explicit bundle assignment, it automatically receives the default bundle.
Deployments are linked to devices (edge connector instances) through registration. When an edge connector starts, it registers itself with a specific deployment. This relationship determines:
Which bundle the connector downloads — the bundle assigned to the deployment.
Which version the connector uses — the target version pinned on the deployment, or the latest if none is pinned.
How the connector appears in monitoring — connectors are grouped by deployment in the admin UI.
A single deployment can have multiple devices (edge connectors) registered to it. Each device independently syncs the bundle and reports its status to the platform.
