2025.10.1

Release date: 30 October 2025

Configurable executor startup delay

A new environment variable (UIPATH_EXECUTOR_STARTUP_DELAY) has been introduced to add a short delay before Executor process creation in unattended Windows sessions. This can be used if the infrastructure requires other processes to start before the Executor starts in the Windows session.

Enhanced Robot Logging Configuration

Robot now supports dual logging with separate log levels for local files and Orchestrator. Use the UIPATH_FILE_LOG_LEVEL environment variable to set a different minimum log level for local file logging while maintaining a separate level for logs sent to Orchestrator.

This allows you to store detailed logs, such as INFO+ levels, locally on the machine while sending only higher-priority logs, such as WARN+ levels, to Orchestrator. Doing so reduces database growth while preserving comprehensive local diagnostic information. Valid values include: Verbose, Trace, Information, Warning, Error, Critical and Off.

Support for large input and output arguments

Starting with this version, the robot supports input and output arguments with more than 10,000 characters.

Support for file arguments for jobs

Starting with this version, the robot supports input and output arguments of type File.

Support for UPN domains

Previously, the smart card authentication for unattended sessions matched the Orchestrator username only to the primary UPN. Changing the UPN domain required recreating smart cards.

You can now specify the UPN on the smart card in the Domain\Username field of your Robot account. Use the ADUPN\some.upn@domain format for private domains, or AzureAd\some.Azure@domain for Azure AD domains.

This update also allows specifying a UPN directly for authentication, regardless of whether password-based or smart card authentication is used.

However, when using smart card authentication with certificates, alternate UPNs are supported only if the certificate was issued to that alternate UPN.

Migrating proxy settings

Updating the Robot using UiPathStudio.msi or UiPathRobot.msi automatically migrates proxy settings from the uipath.config file to %ProgramData%\UiPath\Shared\proxy.json.

Retention period for workflow logs

The retention period for workflow log files has been limited to 30 days by default.

Job ID in execution logs

Robot execution logs now display the job ID.

Smartcard support for headless-with-user mode

Background jobs in headless-with-user mode now also work with smartcard credentials, not just username and password.

Improved log details

Error logs now provide details about the activity that caused your workflow to fail, including the workflow file name, activity name, and container hierarchy. These details help you quickly locate the activity within your project, and are displayed in Studio, Orchestrator, and Robot logs.

HTTPS for all NuGet feeds

Starting with the Robot releases in February 2025 (Latest) and October 2025 (LTS), calls to HTTP-unsecure feeds from NuGet-supported packages are no longer allowed. When a non-HTTPS feed is used, an error is thrown, and opting out of this behavior is not possible.

Transition to secure HTTPS feeds to prevent disruptions.

New options for user sessions

Two new options for the UIPATH_SESSION_BEHAVIOR system environment variable, LeaveSessionActive and LeaveSessionDisconnected, allow you to control what happens to the user session after a job completes.

• UIPATH_SESSION_BEHAVIOR=LeaveSessionActive—Prevents restoration of the initial session state.
• UIPATH_SESSION_BEHAVIOR=LeaveSessionDisconnected—Always disconnects the session on restore.

New UiPath repository certificate SHA-256 fingerprint

If you are using package signature verification, a new UiPath repository certificate SHA-256 fingerprint must be added to your NuGet configuration. Ensure it is added under both trusted authors and trusted repositories, as shown in our documentation.

<certificate fingerprint="A96ADDC7455443CF702A887BC153CF7844038E2E88081D676C57DDD90EC90245" hashAlgorithm="SHA256" allowUntrustedRoot="false" />

Support for Windows Server 2025

Starting with release, UiPath Robot can also run on Windows Server 2025 operating systems.

.NET Framework requirement update

The minimum .NET Framework requirement has been updated from 4.6.1 to 4.7.2.

Bug fixes

• Sometimes, executing jobs would fail with the "Cannot access a closed pipe" or "Connection closed" exceptions. This behavior no longer occurs.
• On rare occasions, using the HTTP Request activity in a Legacy project caused the executor to crash unexpectedly with the error: "System.Exception: Could not retrieve the result of the job execution. This might be because a message was too large to process." The error appeared in Orchestrator for failed jobs.
• In coded workflows, an exception might occur when invoking a workflow multiple times in parallel. This was caused by the use of the RunWorkflowAsync method.
• Using special character quotes " (0x201C) in strings caused a JIT compilation error at runtime in Windows projects.
• The Robot Service incorrectly detected an interactive job as in progress, preventing new jobs from starting. The error message "Another interactive job is running for this user. A user can run a single interactive job at a time." was displayed, even when no jobs were running. This happened due to an improper service-level status update, which caused jobs to get stuck in terminating or stopping states.
• After a machine was idle or locked, the Robot Service failed to reconnect to Orchestrator. It kept using a broken connection indefinitely. The connection to Orchestrator has a finite lifetime, with a default of 30 minutes. You can adjust this duration using UIPATH_HTTP_CONNECTION_LIFETIME, an environment variable that defines the connection lifetime in seconds.
• Repeatedly launching the Robot (picture-in-picture) session caused memory peaks.
• Occasionally, taking a session screenshot caused a UiPath.Session.csharp.exe application error, which prevented robot sessions from closing correctly and new jobs could not start.
• Previously, when a user account existed in multiple domains, it sometimes caused unattended jobs to fail with a session timeout. This happened due to domain confusion during session identification.
• Fixed a FreeRDP bug that caused Robot Service to use a high CPU percentage.
• Occasionally, the robot would report the job was running, even though the Robot Executor already exited.
• Portable Executor now sets the right resolution when running on Windows.
• Packages generated with older Studio versions that used Invoke Workflow activity crashed if the invoked workflow was in a subfolder.
• This version brings several performance fixes.