robot
2025.10
false
- Release notes
- Support for EntraID users with multifactor authentication (MFA)
- Configurable executor startup delay
- Enhanced Robot Logging Configuration
- Support for large input and output arguments
- Support for file arguments for jobs
- Support for UPN domains
- Migrating proxy settings
- Retention period for workflow logs
- Job ID in execution logs
- Smartcard support for headless-with-user mode
- Improved log details
- HTTPS for all NuGet feeds
- New options for user sessions
- New UiPath repository certificate SHA-256 fingerprint
- Support for Windows Server 2025
- .NET Framework requirement update
- Bug fixes
Robot release notes
Last updated Nov 11, 2025
- 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
RunWorkflowAsyncmethod. - 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.exeapplication 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.
