Remote Debugging in UiPath: Connection Types
Uploaded by
Yogesh MemaneRemote Debugging in UiPath: Connection Types
Uploaded by
Yogesh MemaneCommon questions
Powered by AIWith a remote machine connection, UiPath Studio sends the list of project dependencies and activity feeds to the remote robot, which uses these feeds to download the necessary packages. In contrast, for an unattended robot connection, Studio sends only the list of project dependencies, and the remote robot utilizes the Orchestrator feeds and its configured activity feeds to download required packages .
In remote debugging, UiPath ensures that required activity packages are downloaded differently depending on the connection method. With a remote machine connection, activity feeds are provided by Studio, allowing the remote robot to download the necessary packages. For an unattended robot connection, the remote robot relies on Orchestrator and its configured activity feeds for package downloads .
For an unattended robot to be ready for remote execution of processes from UiPath Studio, it must have one of these runtime licenses available: Unattended, NonProduction, or Testing. The robot must also be configured correctly, meeting the version requirements (2021.10.6 or later) and ensuring that the user signed into Studio has appropriate permissions for job initiation and storage management within the same folder context as the target robot .
A known limitation of using remote machine connection for UiPath debugging is that if debugging is paused for an extended period, a connection error might occur in Studio even though the connection remains active on the remote machine. This issue can be mitigated by increasing the TCP idle timeout in your cloud or on-premises load balancer .
When using an unattended robot connection, selecting the 'Picture in Picture' option does not initiate execution in a separate session. This limitation can lead to challenges where the execution must occur within the existing user session, which may not satisfy certain automation scenarios that require session isolation .
The 'Show Live Stream' option in UiPath remote debugging is only available when the robot service on the unattended robot is deployed in service mode. This option is supported exclusively for Automation Cloud Orchestrator and Automation Suite Orchestrator .
Having the remote robot and Studio on the same version is crucial to ensure compatibility and the smooth operation of debugging processes. Version mismatches can lead to issues such as failure to run processes, lack of feature support, or unforeseen errors during execution .
To set up remote debugging in UiPath using a remote machine connection, ensure that TCP/IP connectivity exists between the Studio machine and the remote machine. Both the remote Robot and Studio need to be of the same version. The remote Robot must be connected to the Orchestrator using interactive sign-in or through the machine key with a user also signed in from the Assistant. Additionally, Studio and the target robot should be connected to the same Orchestrator tenant, and remote execution must be enabled .
TCP/IP connectivity is critical for establishing a connection between the Studio machine and the remote machine during remote debugging. However, to prevent connection issues, especially when debugging is paused, it's advisable to increase the TCP idle timeout in your cloud or on-premises load balancer. This measure helps in avoiding errors where the connection appears active on the remote machine but fails in Studio .
To run or debug a UiPath project using an unattended robot connection, Studio, the target robot, and Orchestrator must be running version 2021.10 or later. The robot must have version 2021.10.6 or later. The user signed into Studio must have permissions to start jobs, create, and delete storage buckets and storage files. The unattended robot needs to be configured and the machine should have either an Unattended, NonProduction, or Testing runtime licenses available .