September 2026 release notes for Automation Cloud.

Model impact, a new tenant-level tab in Model hub, shows where each AI model is used across your organization: which products, features, and processes depend on it, how often they call it, and when they last used it.

Deprecating, replacing, or reconfiguring a model changes the behavior and cost of every automation behind it. Model impact gives you that scope before you act, so you can assess the risk, prioritize migration work by actual usage rather than guesswork, and plan upgrades instead of finding broken automations afterward. It also gives compliance reviews a clear record of which automations depend on which models.

For details, see Model impact and Reviewing model impact.

Model hub in the AI Trust Layer is now generally available. Administrators and compliance teams get a central view of how LLMs are used across UiPath products, for every tenant in the organization, including the provider and model behind each product feature, its routing region, and its lifecycle status.

At the tenant level, you can configure routing regions and supported models, replace UiPath-managed models with your own subscription or model, and review the history of configuration changes. Combined with AI Trust Layer policies, these controls help you enforce data-residency requirements and prepare for model migrations before a deprecation affects your automations.

For more information, see Model hub and Managing models in Model hub.

Document Understanding models now appear in the Model hub tenant grid and can be managed from Model hub. Previously, they were not available there.

For more information, see Model hub.

You can now power the Close Popup semantic activity in UI Automation with your own large language model subscription instead of the UiPath-managed subscription, using one of the supported models.

For more information, refer to:

Deleting a Relay Group now immediately stops all Relay clients connected to it. Before removing a group, confirm that no active workflows depend on it, as client connections are terminated without a drain period.

For details, see Configuring a Relay group.

You can now retrieve, per tenant, the number of allocated and in-use robot runtimes through the platform API. Previously, this information was only available at the organization level.

You can now retrieve a consumption breakdown by process for a tenant through the platform API, with support for pagination, sorting, filtering, and an optional per-service breakdown.

For details, see Get Tenant Consumption by Process.

Supported TCP-based connections, such as SAP BAPI, now work when you run the Relay client as a container. The on-prem executor ships as its own container image, registry.uipath.com/relay-onprem-executor, and runs as a second container that shares a network namespace with the Relay client. This lifts the container limitation noted in the September 4 entry below.

Container support for the executor covers Docker and Podman and requires Relay client 26.4.3 or later with the matching executor image tag. You supply the SAP JCo libraries in a directory mounted into the executor container; no Java runtime is needed on the host.

For details, see SAP BAPI and other TCP-based connections.

Relay access is now controlled by dedicated Relay permissions instead of Automation Cloud administrator group membership. Tenant Administrators can create, edit, and delete Relay Groups without an Organization Administrator role, and custom roles can grant granular Relay access: Relay group (View, Create, Edit, Delete), Relay client (Delete), and Relay group config (View).

Custom roles that previously granted Relay visibility through the Centralized Access Administration page permission no longer have access to Relay Groups. Those roles must be updated to include Relay > Relay group > View. Organization Administrators and Tenant Administrators are unaffected.

For details, see Configuring a Relay group and Roles.

Relay now reaches supported on-premises systems that use protocols other than HTTP. The first supported connection is SAP BAPI, which uses SAP's RFC protocol over TCP.

Relay routes these calls through the on-prem executor, a Java process that the Relay client starts and supervises on the same host. The executor listens on the loopback interface only and accepts no connections from outside the host.

Using a TCP-based connection requires Relay client 26.4.3 or later, a Java 21 or later runtime on the Relay host, and the connector's libraries in a directory you provide. Arbitrary TCP passthrough is not supported, and the on-prem executor is not available when you run the Relay client as a container.

For details, see Supported TCP-based connections and On-prem executor for supported TCP-based connections.