UiPath Documentation
robot
2026.10
false
Robot release notes
  • Release notes
    • 2026.10.0
    • Robot JavaScript SDK Release Notes
      • 1.2.7
      • 1.2.8
      • 1.2.9
      • 1.3.0
      • 1.3.1
      • 1.3.2
      • 1.3.3

2026.10.0

2026.10.0 release notes for Robot.

Release date: November 12, 2026

Agents, functions, and API workflows​

Unattended robots on Windows run agents, functions, and API workflows next to RPA processes and test cases. The feature is generally available. Jobs run on the Local runtime type and use the Agent slots and Function slots of the machine template. Functions and API workflows can also run on your Unattended licenses, with Use Production (Unattended) on the machine template. Refer to Unified Runtime.

New features and improvements​

  • EntraID users with multifactor authentication (MFA). Unattended robots can use EntraID users that have MFA enabled. Refer to Using EntraID users with multifactor authentication (MFA) for unattended robots.
  • Machine-level proxy. Robot processes can take their proxy configuration from the machine-level proxy.json file, enabled through the UIPATH_APPLY_SERVICE_PROXY environment variable.
  • Encrypted proxy password. The proxy configuration accepts an EncryptedPassword field, a DPAPI LocalMachine ciphertext used when the Password field is empty.
  • Proxy credentials command. The setproxy command of the Robot command line interface sets proxy basic authentication credentials for the current user. Refer to Set proxy basic authentication credentials.
  • Medium+ integrity per invocation. Invoke Workflow File, when invoked isolated, and Invoke Process can run at the Medium+ integrity level, through the UIPATH_MEDIUMPLUS_INVOKE machine environment variable. It requires UiPath.System.Activities 26.6.0 or later. Refer to Robot Executor.
  • Verbose log cap. The Robot sends at most 10,000 verbose logs per executor process to Orchestrator, then logs a warning and doesn't send further verbose logs from that process. Logs from the Log Message activity don't count, the local log file isn't capped, and you can change the limit with UIPATH_VERBOSE_LOG_LIMIT. Refer to Logging levels.
  • Accurate licensed job time. The Robot reports how long each job ran, so time spent disconnected from Orchestrator no longer counts as execution time.
  • Richer failure logs. Workflow failure logs include the full .NET exception details and structured error information.
  • Robot version in execution logs. Execution logs include the robotVersion field, the version of the Robot that ran the job. Refer to Log fields.
  • NuGet cache cleanup. The cleannugetcache command deletes global-packages entries that weren't accessed in the last 30 days by default, and wipes the NuGet HTTP cache. Refer to Clean NuGet cache.

Breaking changes and deprecations​

  • The UiPath Platform Installer replaces the MSI installers. One installer now sets up the Robot and the other desktop clients, and applies updates in the background, without a full reinstall. Use the online UiPathPlatformLTS.26.10.msi installer, or, for machines without internet access, the offline installer: a single EXE that includes the full 2026.10 package, with Delegate. UiPathRobot.msi and UiPathStudio.msi don't ship for 2026.10. Robot 2025.10 and earlier keep receiving patches on the classic MSI until their end of support. Refer to Installing the Robot.
  • The Update Service doesn't ship. Orchestrator update policies no longer apply to 2026.10 robots. The Platform Installer updates the Robot on its update channel. Refer to Updating the Robot.
  • Machine key connections are deprecated. Robots connected with a machine key still run RPA processes and test cases, but by default they don't run agents, functions, or API workflows. Use client credentials instead. Client credentials use expiring tokens, while a machine key uses a token that never expires. Refer to Client credentials and machine keys.
  • The Robot installs in its own folder, separate from Studio. Scripts or tools that reference Robot executables by full path need the new location. Refer to Install folder.
  • The Robot runs on .NET 10. The Platform Installer installs the .NET 10 runtime with the Robot. The Windows and cross-platform executors run on .NET 10, while the Windows - Legacy executor remains on .NET Framework 4.7.2. Refer to Robot Executor.
  • Live streaming and remote control is opt-in. Live streaming and remote control (RealVNC) is not installed by default by the Platform Installer. To use it, select Live streaming and remote control in the installer, or set INSTALL_LIVE_STREAMING=true for a silent installation. Refer to Robot options.

For what to do before you upgrade, refer to Upgrading from 2025.10.

Was this page helpful?

Connect

Need help? Support(opens in new window)

Want to learn? UiPath Academy(opens in new window)

Have questions? UiPath Forum(opens in new window)

Stay updated