Runtime & Versioning

Select, validate, and upgrade the Agent Executor version that runs your agent.

Runtime & Versioning controls the Agent Executor version that runs your agent. Executor releases add capabilities, address issues, and can deprecate earlier behavior. Pinning a version keeps runtime behavior predictable while you validate upgrades.

Open Manage Agent → Runtime & Versoning. The navigation label currently uses Versoning.

Executor Version

Use Executor Version to select the runtime for this agent.

Field	Obligation	Default	Notes
Executor Version	Mandatory	The latest version available to your tenant, such as 1.4	Switching versions can change agent behavior and available features.

The dropdown lists versions available to your tenant. New agents use the latest available version by default. Existing agents remain on their current version until you migrate them.

Agent Executor v1.4 is available. Migrate agents on earlier versions after validation.

Migrate to v1.4

Agent Executor v1.4 is the current documented upgrade target. Migrate when you need its runtime capabilities or support for the current release.

1. In Executor Version, select 1.4.

2. Select Save.

3. Test representative conversations, skills, and integrations.

Check expected outputs and execution behavior before you rely on the upgraded agent in production.

An executor upgrade can change agent behavior. Validate the agent before migrating production workloads.

See September 12 release notes for the v1.4 announcement.

When the executor version matters

Most agent configuration works across versions. Some capabilities require a newer executor version. For example, PII tokenization can be unavailable when an agent uses an older unsupported version.

If a builder section is unavailable, check the executor version. Upgrade and validate the agent when the feature requires a newer runtime.

Draft versions and executor versions

Executor Version selects the platform runtime. Draft Version saves a snapshot of the agent configuration.

Version type	Scope	Use it for
Executor Version	One runtime per agent	Control runtime behavior and feature availability
Draft Version	Many snapshots per agent	Compare or restore agent configuration

The settings are independent. Saving a draft doesn't change the executor version. Changing the executor version doesn't save a draft.

Why this matters

Version pinning makes agent behavior reproducible. Your agent remains on its tested runtime until you choose an upgrade. Use the latest supported version for new agents, then validate it before production use.