Octobre 2026

October 2026 release notes for Test Cloud.

October 1, 2026

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.

Pour connaître la disponibilité actuelle des modèles sur la plate-forme UiPath, consultez Fonctionnalités d'IA et routage des modèles. Pour plus d'informations, consultez la chronologie d'obsolescence du modèle 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.