Why Incorrect Hostnames For The Execution Target Are Being Displayed When Configuring A Trigger In Orchestrator?

News Knowledge Base
1

Why incorrect Hostnames for the Execution Target are being displayed when configuring a Trigger in Orchestrator?

Issue Description: When setting up a Trigger on a Queue, there are 3 options.

  1. Account
  2. Machine
  3. Hostname

After selecting the right Account and Machine, the Hostnames are not correct and are not associated with the Account/ Machine chosen. It is not possible to find where in Orchestrator this is configured. Where to setup the Hostnames that would appear in this list? How to remove invalid values from this list?

Resolution: This is an expected behavior for Cloud, Automation Suite and On-Premise Orchestrator versions.

  1. After selecting a machine template, the Hostname option is displayed, allowing to select the desired workstation/robot session to execute the process.

All available sessions in the active folder are displayed, either unconnected, disconnected, or connected.

  1. The hostname list will contain the values from the [dbo].[Sessions] table. It will allow to select a session. If in the past if that machine template is already used for another Robot connection, it will allow to select that in the Hostname, even if based on the actual requirement is not valid anymore.

  1. Only Unattended runtimes can be used to configure the mapping. Make sure the required Unattended runtime license(s) to execute the job is allocated to the associated machine template.

  1. In order to get rid of the old/not-used Unattended sessions, soft delete (set the IsDeleted to 1) them from Orchestrator -> Tenant -> Monitoring -> Unattended sessions -> and then, observe the problematic session(s) in the Hostname for the triggers.

  1. If the Robot is connected to Orchestrator, but still not seen it in the trigger's Hostname field, that means either it is connected via a Service URL in UiPath Assistant (Attended Robot connection), or connected to a different Orchestrator URL or tenant, or connected via a Machine Key or Client ID to a different Machine Template.

  1. Ensure installing the Robot in Service Mode. If in the Robot machine -> Start -> services.msc -> If not found in the list of services the UiPath Robot service, which means the Robot is installed in User Mode.

  1. In UiPath Assistant -> Preferences -> Orchestrator settings -> choose the Client ID connection type -> provide Orchestrator URL, Client ID, and Client Secret -> Connect .

Note: For the Client ID credentials connections, UiPath Robot 2022.2 or higher is required.