Description
Dynamic allocation
Allocate Dynamically
Dynamic allocation with no explicit account and machine selection allows you to execute a foreground process multiple times under the account and machine that become available first. Background processes get executed on any account, regardless if it's busy or not, as long as you have sufficient runtimes.
Using the Allocate Dynamically option you can execute a process up to 10000 times in one job.
Account
The process is executed under a specific account. Specifying only the account results in Orchestrator allocating the machine dynamically. Specifying both the account and the machine template means the job launches on that very account-machine pair.
Machine
The process is executed on one of the host machines attached to the selected machine template. Specifying only the machine template results in Orchestrator allocating the account dynamically. Specifying both the account and the machine template means the job launches on that very account-machine pair.
Note: Make sure the required runtime licenses to execute the job are allocated to the associated machine template.
Hostname
After selecting a machine template, the Hostname option is displayed, allowing you 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.
Note: Only unattended runtimes can be used to configure the mapping. Make sure the required runtime licenses to execute the job are allocated to the associated machine template.
Select valid account-machine mappings
The process can be executed on specific account-machine pairs. Learn more about account-machine mappings.
Note:
-
A warning is displayed upon selecting a hostname that is not active (i.e., with the Unresponsive or Disconnected status).
-
Accounts part of mappings that are employed in triggers cannot be deleted or unassigned from the folder the trigger resides in. Make sure the account is not set as an execution target in a trigger so you can delete them.
