What is orchestrator tenant

[Gokul001 (Gokul Balaji)]

@vineelag

what is the difference between the robots and machine in Orchestrator

Check out this thread

Difference between Robot and Machine

I think the documentation above has a pretty good description but to take it a step back essentially Machine is your physical or virtual computer host Robot can be referring to the “Service” which is listening and waiting on the machine for instruction to run a process, in the case of creating a Robot record in Orchestrator you are assigning two properties a Machine and user credential to define the profile in which the Robot Service will run the process under.

Robots:

1. Role: Robots are the software automation agents that perform the actual automation tasks or workflows. They execute the processes that you design in UiPath Studio or other UiPath tools.
2. Execution: Robots run automation jobs or processes on target systems, interacting with applications and data as instructed in the automation workflows.
3. Configuration: You can configure various properties for Robots, such as their name, type (Attended, Unattended, etc.), and environment. You also define which processes or automation tasks a Robot can execute.
4. Licenses: Robots consume licenses in Orchestrator, and you need to allocate a license to each Robot to enable them to run processes.
5. User Assignment: Robots can be associated with specific users or can run processes without user interaction, depending on their type (Attended, Unattended).
6. Status: You can monitor the status of Robots in Orchestrator, track their performance, and view logs of their activities.

Machines:

1. Role: Machines, in Orchestrator, represent the physical or virtual computers where your Robots are installed and can run automation processes. Each Machine typically corresponds to a specific device or server.
2. Connection: Machines act as a link between Robots and the physical or virtual workstations where the automation is executed. They facilitate the communication between Orchestrator and the Robots.
3. Configuration: You define the name of the Machine, and you associate one or more Robots with it. The Robots that are associated with a Machine can use it as their runtime environment.
4. Purpose: Machines help Orchestrator understand where the Robots are installed, allowing you to allocate automation tasks to specific Robots installed on specific Machines.
5. High Availability: Machines can be used to ensure high availability of automation. If one Machine is unavailable, Orchestrator can redirect automation tasks to a backup Machine with available Robots.