Remote Debugging

Uploaded by

Yogesh Memane

Available Formats

Download as XLSX, PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

17 views

Remote Debugging

Uploaded by

Yogesh Memane

Available Formats

Download as XLSX, PDF, TXT or read online on Scribd

You are on page 1/ 5

Topic Sr.

Remote Debugging 1

6
7
Pointers
Remote debugging in UiPath extends your debugging capabilities to scenarios where your automation runs on mach
with different configurations, including remote machines.
It allows you to connect to and debug robots deployed on those remote machines using two methods: a direct TCP/
connection to the remote machine or through Orchestrator for unattended robots in the same tenant.

Two available connection type from studio for remote debugging are:
a. Through Remote Machine
b. Through Unattended Robot

To run or debug a project remotely using a Remote Machine Connection

a. Make sure:
TCP/IP connectivity exists between the Studio machine and the remote machine.
The remote Robot is the same version as Studio.

b. Meet the condition for remote robot

If interactive authentication is enforced in Orchestrator and you want to run or debug an unattended process, make
that the remote robot meets one of the following conditions:
i. Connected to Orchestrator using interactive sign-in.
ii. Connected using the machine key and a user is also signed in from the Assistant.
iii. Connected using the machine key, no user is signed in from the Assistant, and a troubleshooting session is enable
Orchestrator for the machine. For more information, see Debugging Unattended Processes.

c. In studio
Set up a connection to the remote robot.
Make sure remote execution is enabled.
Run or debug your project.

To run or debug a project remotely using an Unattended Robot connected to Orchestrator, you should:

All the prerequisites are met:

Studio and the target robot are connected to the same Orchestrator tenant.
Studio, the target robot, and Orchestrator are running version 2021.10 or later. For the robot, 2021.10.6 is the minim
version required for running projects from Studio versions starting with 2021.10.6.
The user signed in to Studio has permissions to start jobs, and to create and delete storage buckets and storage files
same folder context as the target robot. In addition, the robot account must have view permissions for storage buck
and storage files.
The unattended robot is configured and the machine has one of the following runtime licenses
available: Unattended or NonProduction or Testing

For debugging foreground processes, the option Run foreground automations is enabled for the robot in Orchestrat

Depending on the type of connection used for remote debugging, the remote robot gets the activity packages requi
execute a project as follows:
i. Remote machine connection - Studio sends the list of project dependencies and activity feeds (package sources) t
remote robot, which uses the feeds provided by Studio to download the required packages.

ii. Unattended robot connection - Studio sends only list of project dependencies to the remote robot, which uses th
Orchestrator feeds and the activity feeds configured on the remote robot to download the required packages.

Known limitations
When you use a remote machine connection, if you pause debugging for an extended period of time, a Connection
error might occur in Studio even though on the remote machine the connection still appears to be active. To avoid t
issue, you can increase the TCP idle timeout in your cloud or on-premises load balancer.

Remote debugging long-running workflows is only supported for unattended robot connections.
When you use an unattended robot connection, selecting the Picture in Picture option does not start execution in a
separate session.
The Show Live Stream option works only if the robot service on the unattended robot is deployed in service mode.

The Show Live Stream option is only supported for Automation Cloud Orchestrator and Automation Suite Orchestra
Any one of the following and not all the conditions