Oktober 2026

October 2026 release notes for Robot.

October 22, 2026

Build number: 2026.0.204

Verbesserungen

• Robots connected to Orchestrator with a machine key no longer run agents, functions, or API workflows. RPA processes and test cases still run. The Robot now logs an error every time it connects with a machine key. To run agents, functions, and API workflows, connect the Robot with client credentials. For more information, see Connecting unattended robots to Orchestrator.
• The Robot now keeps a pool of warm Python processes on Windows, so Python agents and functions start faster.
• The GovCloud domains are now in the default allow list of the Robot JavaScript SDK.

Fehlerbehebungen

• Fixed an issue where the installation logs of a low-code agent contained errors that did not affect the installation.
• Fixed an issue where a coded Python agent or function asked for extra configuration of the Python interpreter, even when Python was installed on the machine.
• Fixed an issue where a job set to use the machine's Python did not fall back to the managed Python when the machine's Python could not run the job.

6. Oktober 2026

Build number: 2026.0.203

Verbesserungen

• To prevent a job from exhausting the Robot's memory when the logging level is set to Verbose, the Robot now keeps at most 10,000 verbose logs per executor process. When the limit is reached, the Robot logs a warning and drops further verbose logs from that process. For more information, see Configuration files.

Fehlerbehebungen

• Fixed an issue where unattended jobs on Azure Virtual Desktop could fail to start with the error The user name or password is incorrect followed by The network location cannot be reached, when the Robot signed in while the previous session was still being closed. The Robot now retries the sign-in for a limited time in this case.
• Fixed an issue where, if the Robot lost its connection to Orchestrator while a job was running, the time until the connection was restored was counted as job execution time for licensing. The Robot now reports how long each job actually ran, and Orchestrator uses that duration instead of the times at which it received the job updates.