- Release Notes
- Getting Started
- UiPath Assistant
- Installation and Upgrade
- Robot Types
- Robot Components
- Licensing
- Connecting Robots to Orchestrator
- Processes and Activities
- Logging
- Robot JavaScript SDK
- Specific Scenarios
- Restarting Robot Components
- Windows Sessions
- Login Using Thales Luna Credential System
- Login Using NShield Key Storage Provider
- Redirecting Robots Through a Proxy Server
- Executing Tasks in a Minimized RDP Window
- Using Mapped Network Drives
- Stopping a Process
- Disable Stop Button
- Custom Package Folders and Network Paths
- CrowdStrike Integration
- Robot Citrix Apps Virtualization
- Troubleshooting
- Common Connection Errors
- Unresponsive Robot Over RDP
- Duplicate Execution Logs
- Frequently Encountered Robot Errors
- Increased Process Execution Duration
- Enforced Package Signature Verification
- Message Too Large to Process
- Errors When Running as Administrator
- NuGet Packages Not Accessible After Migration
- User Access Control Prompt and UI Automation Activities
- .NET required during installation
- Assembly Cannot Be Loaded From Network Or Azure File Share
- Activities cannot find .NET Runtime
2023.10.5
Release Date: April 3, 2024
UIPATH_PRESERVE_CREDENTIALS_CASE
. Add it to your environment, and set its value to True
.-
We've fixed the issue where users were unable to log into their Virtual Desktop Infrastructure (VDI) accounts. This primarily occurred when a previous user did not log off after manually stopping an unattended automation via Orchestrator.
-
When authenticating through client certificates, a bug prevented the robot from reading private keys from card readers. This mainly occurred when multiple card readers were present and at least one had unexpected issues.
-
Previously, sessions might have remained in use after a job was completed due to an incorrect status of the executor’s exit. The system now automatically terminates the executor 30 seconds after a job is completed.
-
An issue causing Assistant to throw the
Format string contains an unescaped latin alphabet character
error when running a job has been resolved.