2026 年 10 月

October 2026 release notes for Test Cloud.

October 20, 2026

Solutions now available in India

Added October 21, 2026: This feature was released on October 20, 2026 but was not included in the release notes at the time.

Solutions is now available in the India region with full data residency. For more information about regional availability, see Global cloud regions.

October 16, 2026

Input/output saving for audit is off by default in new AI Trust Layer policies

Prompt inputs and LLM-generated outputs are no longer saved in the audit logs by default for new AI Trust Layer policies. Input/output saving is disabled when you create a policy, so LLM calls governed by the policy appear in the audit logs with their inputs and outputs shown as Blocked by Policy until you enable it. Existing policies keep their current setting.

For details, refer to Viewing audit logs and Settings for AI Trust Layer policies.

October 14, 2026

Removed: Claude Sonnet 4

Claude Sonnet 4 (anthropic.claude-sonnet-4-20250514-v1:0) is no longer available on the UiPath platform. UiPath removed it on 2026-10-13, following its retirement by Amazon Bedrock. Claude Sonnet 4.6 (anthropic.claude-sonnet-4-6) is the replacement.

UiPath-managed models are migrated to Claude Sonnet 4.6 automatically, with no action required on your side. Configurations that bring your own models through AI Trust Layer and reference Claude Sonnet 4 are invalidated. If you have not updated them to Claude Sonnet 4.6, they fall back to UiPath-managed models.

UiPath Platform 全体で利用可能な現在のモデルについては、「 AI 機能とモデルのルーティング」をご覧ください。詳しくは、「 LLM モデルの非推奨化のタイムライン」をご覧ください。

Model Hub improvements for Bring Your Own (BYO) configurations

Model Hub now shows the status of Bring Your Own (BYO) configurations, lets you check the status of enabled configurations, and lets you enable disabled configurations. You can also optionally display the Folder column and see more context when deleting a BYO configuration. For details, see Managing models in Model hub and Configuring LLMs.

October 13, 2026

Relay support for Snowflake and SQL Server connections

Private (Relay) connections for the Snowflake connector and for SQL Server in the Database Hub connector now run through the Relay on-prem executor. The JDBC drivers ship inside the executor, so no connector libraries or dependencies directory are needed. Requires Relay client 26.4.4 or later. Other Database Hub database types remain unsupported over Relay.

For details, see Supported TCP-based connections.

Relay client 26.4.4

Relay client 26.4.4 adds the following:

• relay restart --all and relay restart <id1>,<id2> restart several Relay groups one at a time, for example after extracting a new Relay client archive, and end with a summary of restarted and failed groups.
• relay describe shows the organization and tenant names the Relay client is registered to and, after a failed start, ends with the last error and a recovery hint. The --json output adds organization_name, tenant_name, and hint alongside the existing last_error.

For details, see Command reference.

October 7, 2026

Governance policy for auto-acquiring AI and Agentic usage top-ups

Organization Administrators can configure a governance policy in AI Trust Layer that lets users automatically acquire AI and Agentic usage top-ups instead of requesting them manually each time. This feature is being rolled out gradually and might not yet be available for your organization.

For details, refer to Settings for AI Trust Layer policies, Granting AI and Agentic usage top-ups, and Requesting AI and Agentic usage top-ups. For the Automation Ops release note, refer to the October 2026 Automation Ops release notes.

October 5, 2026

Improvements to the Consumables Center

• Folders with no consumption in the selected period no longer appear in the Folder Consumption list, reducing clutter without changing your folder structure. For details, see Understanding the Consumables Center.
• Streamlined status indicators in the Consumables Center by removing the organization-level status badge, the tenant status badge for tenants with no allocation or no consumption, and merging the Critical tier into Warning for tenants at or above 70% consumption. For details, see Understanding the Consumables Center.

Cloudflare IP range might be required for any UiPath service

Allowlisting the Cloudflare 104.16.0.0/13 outbound IP range might be required for any UiPath service, not only Document Understanding as announced in the July 2026 release notes. If your firewall restricts outbound traffic and your network equipment does not support DNS-based allowlisting, allow this range to prevent traffic from being blocked. DNS-based allowlisting is recommended because Cloudflare IP ranges are broad and may change.

詳しくは、「Test Cloud 向けにファイアウォールを設定する」および「レガシ - Test Cloud 向けにファイアウォールを設定する」をご覧ください。

2026 年 10 月 1 日

Removed: gpt-4o-2024-05-13

gpt-4o-2024-05-13 is no longer available on the UiPath platform. UiPath removed it on 2026-09-30, following its retirement by Azure OpenAI. gpt-5.1-2025-11-13 is the replacement.

UiPath-managed models are migrated to gpt-5.1-2025-11-13 automatically, with no action required on your side. Configurations that bring your own models through AI Trust Layer and reference gpt-4o-2024-05-13 are invalidated. If you have not updated them to gpt-5.1-2025-11-13, they fall back to UiPath-managed models.

UiPath Platform 全体で利用可能な現在のモデルについては、「 AI 機能とモデルのルーティング」をご覧ください。詳しくは、「 LLM モデルの非推奨化のタイムライン」をご覧ください。

Bring your own guardrail subscription [Preview]

You can now bring your own guardrails into the AI Trust Layer, using your organization's own safety vendor subscriptions. Agent guardrails are then evaluated by your provider, under your own region and vendor agreement. During preview, you can bring subscriptions to Azure AI Language, Azure Content Safety, or Noma.

This helps organizations that cannot send prompt content to a provider they have not vetted, that have data residency requirements to meet, or that already pay for a safety service and want to reuse it across their agents. Your provider's guardrails sit alongside the UiPath-managed ones and work the same way, with the same scopes and actions: agent developers apply them to individual agents, and administrators enforce them organization-wide.

Every evaluation is recorded in the agent trace together with the provider that ran it, so you can account for which checks fired and where. Each guardrail can also fall back to its UiPath-managed equivalent if your provider becomes unreachable, so enforcement never depends on a single vendor staying available.

For details, refer to Configuring guardrails.