UiPath Robot

The UiPath Robot Guide

Release date: 12 December 2018

What’s New

With Citrix environments being so popular, we are further extending automation capabilities with native support for Citrix XenApps. Once the Citrix Remote Runtime component is deployed on all the Citrix server machines and the new Citrix extension is installed on the client machine, elements in such environments are natively detected by Studio and the Robot. As such, selectors are properly built, without any hassle. If this raises your interest, get all the details from here.


A notable addition in this newest release, Smart Card Robot Authentication is now here to handle Common Access Cards and Personal Identity Verification support. As such, Unattended, Development, and NonProduction Robots can simply use your SmartCard to start sessions on machines, besides the conventional way. The connection method is easily selected when a Robot is created or edited. Check out how it is done on this page.


Do you think Attended Floating Robots are sweet? Good! Because the Floating Robots feature has been augmented to incorporate Development Robots as well. This is a major step forward in ensuring better, more convenient resource management of your Non-Persistent VDIs and hotseat environments. Create and configure your Development Floating Robots and connect to them from any defined machine.

This, paired with the fact that you can now activate your Studio license from Orchestrator through the Robot that connects them, makes for a broader automation experience, since workflows can be executed, modified, and debugged with Development Floating Robots. For more information, click here.


Fancy using the command line? You might want to know that starting processes this way is now a thing on all Robots, regardless of their type. As long as a process is available for the Robot Agent (Tray), it can be started with a simple command, as well as with arguments. Used along with the Windows Task Scheduler, it is an efficient way to have processes started as soon as a user logs in. The appropriate process is downloaded by the Robot before execution, or updated if necessary.

User Experience

Intended to make collaboration with Attended Robots easier, the Robot Agent (Tray) displays the currently running process in an individual widget, while allowing you to pause, resume, or stop the execution. Not only does this help you keep an eye on what the Robot is doing, but also to pause the execution in case something unexpected happens and resume once everything is in order. Find out more on this page.

Also, to facilitate identifying which step the Robot is performing at any given time, we have created the Report Status activity and added it to the System activities pack, which enables you to create a custom status message that is displayed in the Robot Tray at any point in the execution of a workflow.

Breaking Changes

  • Microsoft.Activities v.1.0.1 and Microsoft.Activities.Extensions v2.0.6.9 are no longer packaged in the UiPathStudio.msi installer. More information about this is available in the here.

Known Issues

  • Upgrading your Citrix client from Citrix Receiver to Citrix WorkSpace requires you to reinstall the UiPath Citrix extension. Find out more on this page.
  • The Citrix Receiver and Citrix WorkSpace are also available as Universal Windows Platform (UWP) applications. You can not install the UiPath Citrix Extension for these applications. Please use the standard Citrix Receiver or Citrix WorkSpace. You can find more information here.
  • Native Citrix automation does not currently support high DPI. You can prevent possible issues by disabling the DPI scaling options in your Citrix Receiver or Citrix WorkSpace client. Read more about it here.
  • Because of ICA and RDP cross-protocol compatibility issues, you need to restart all your active Citrix sessions after installing the UiPath Remote Runtime and UiPath Citrix Extension. More information is available here.
  • Lengthy executions in Citrix environments can often result in failure. This is caused by known limitations in the WPF Renderer, which interrupt process execution if the Citrix application session reaches the timeout limit.
  • Because of a limitation in NuGet libraries, the fully qualified file name or path must be less than 260 characters.
  • Connecting the Robot to Orchestrator during a paused process execution shows the Robot as connected, but unlicensed.
  • Input arguments are not displayed in Orchestrator for a process started with input and output arguments from the command line.
  • Sending text to an editable combo box, such as a save dialog, often results in the text not being sent. This is because of a known limitation of the Active Accessibility property in editable combo boxes.

Bug Fixes

  • Particular Kanji characters were not identified by the Click Text activity.
  • On rare occasions, the Java extension failed to install if it was already on that machine and the deployment path was too long.
  • UIExplorer would throw an error when trying to select particular text strings from a HTML file opened in Internet Explorer or Chrome.
  • The user got disconnected from a RDP machine on which a Robot was executing a process. This only happened on Windows 10 Enterprise N 1709 versions and higher.
  • Trying to install the UiPath Silverlight extension without having the Silverlight runtime library installed would throw an exception.
  • The Type Into, Click, and Click Image activities would considerably reduce the process execution performance when used on Internet Explorer.
  • Selectors were not generated for elements inside IFrames on pages opened in Chrome.
  • Errors generated by incorrect selectors indicated it was triggered by the UiPath.Executor rather than the corresponding activity.
  • Some Katakana characters were inconsistently sent when used with the Type Into activity.
  • Sending the Alt + F4 hotkey to an IE instance under high load would often fail to close it.
  • Click Trigger events were not detected when used on the Adobe Reader DC application.
  • If you locked the screen of a machine over an active RDP session during a process execution, you would have been unable to log back into the machine until restarting it.

Updated about a month ago


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.