A job represents the execution of a process on a UiPath Robot. You can launch the execution of a job in either attended or unattended mode. You cannot launch a job from Orchestrator on attended robots, unless for debugging or development purposes.
Attended jobs can be triggered from the UiPath Assistant or the Robot Command Line Interface. Unattended jobs are launched from Orchestrator, either directly on the spot from the Jobs or Processes page, or in a preplanned manner through triggers, on the Triggers page.
The Jobs page represents the jobs control center, where you can monitor launched jobs, view their details and logs, and stop/kill/resume/restart a job.
Click for field descriptions for the Jobs page
The name of the process.
The machine object used for connecting the executing infrastructure to Orchestrator.
The name of the workstation used for execution.
The identity under which the execution takes place. The following values are possible:
Note: For Robots older than 2021.10, the host identity gets populated dynamically according to the account settings made in Orchestrator. Changing the
Known Issue: Filtering by host identity on the Jobs and Logs pages does not work correctly for jobs executed via accounts without credentials. When running jobs on Windows machines, the Host Identity column is populated with the actual identity of the robots (domain\username), however, filtering by this value returns no jobs. When running jobs on Linux machines, jobs are executed under Root, however, this value is not available for filtering.
The type of job according to where the execution takes place and depending on whether the robot impersonates a user or not:
The runtime type used for execution.
The state of the job. See details about job states.
The priority of the job. See details about job priorities.
The amount of time since the job has started executing. Hovering over this field displays the exact start time and date.
The amount of time since the job has finished executing. Hovering over this displays the exact end time and date.
The agent of the execution.
When starting a job or defining a trigger, you can define specific account-machine pairs on which execution takes place. Account-machine mappings enable you to tie unattended usage under particular accounts to specific machine templates. The gives granular control over the execution targets of your automation. Account-machine mappings can be tenant-based (not tied to a specific folder), or folder-based (tied to a specific folder).
Learn how to configure account-machine mappings.
根据在 Orchestrator 中启动作业的机制，您可以隐式选择和配置作业分配策略和执行目标。本文介绍了从“作业”页面启动作业时可用的分配策略和执行目标。
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.
使用“动态分配”选项，您可以在一个作业中最多执行一个流程 10000 次。
The process is executed under a specific user or robot account. Only specifying the account results in Orchestrator allocating the machine dynamically. Specifying both the account and the machine means the job launches on that very account-machine pair.
The process is executed on one of the host machines attached to the selected machine template. Specifying the template displays an additional Connected Machines option, allowing you to select a specific host machine from the pool of connected host machines. Only specifying the machine results in Orchestrator allocating the account dynamically. Specifying both the account and the machine means the job launches on that very account-machine pair.
You need to provision a Windows user for each account on a host machine that belongs to the folders to which the corresponding machine template is assigned.
Say you connected a server to Orchestrator using the key generated by the machine template, FinanceT. That machine template is assigned to folders FinanceExecution and FinanceHR, where 6 accounts are assigned as well. Those 6 accounts need to be provisioned as Windows users on the server.
- 1 个文件夹
- 1 个带有两个运行时的计算机模型
- 2 accounts: john.smith and petri.ota
- 2 个需要用户交互的流程：P1 - 将队列项目添加到队列，P2 - 处理队列中的项目
- The machine template and the aacounts must be associated to the folder containing the processes.
- 任何人都以高优先级执行 P1。
- P2 由 petri.ota 以低优先级执行。
- Start a job using P1, don't assign it to any particular account, set the priority to High.
- 启动 P2 的作业，将其分配给 petri.ota，将优先级设置为“低”。
The priority is inherited from where it was initially configured. You can either leave it as it is or change it.
Automations Page > Jobs
Inherits the priority set at the process level.
Automations Page > Triggers
Inherits the priority set at the trigger level. If the trigger itself inherited the priority at the process level, then that one is used.
Automations Page > Processes
Uses the priority set for that process.
The priority is set by default to Inherited, meaning it inherits the value at the process level. Choosing a process automatically updates the arrow icon to illustrate what value has been set at the process level. Any jobs launched by the trigger have the priority set at the trigger level. If the default Inherited is kept, the jobs are launched with the priority at the process level.
Any subsequent changes made at the process level are propagated to the trigger, and the jobs created through it implicitly.
如果您启动的作业需要用户干预同一台未在 Windows Server 上运行的计算机上的多个机器人，则所选流程仅由第一个机器人执行，而其余流程将失败。将为每个执行创建一个实例，并将其显示在“作业”页面上。
如果您从同一台 Windows Server 计算机上的多个高密度机器人上启动作业，则意味着所选流程由每个指定的机器人同时执行。将为每个执行创建一个实例，并将其显示在“作业”页面上。
If you are using High-Density Robots and did not enable RDP on that machine, each time you start a job, the following error is displayed: “A specified logon session does not exist. It may already have been terminated.” To see how to set up your machine for High-Density Robots, please see the About Setting Up Windows Server for High-Density Robots page.
For unattended faulted jobs, if your process had the Enable Recording option switched on, you can download the corresponding execution media to check the last moments of the execution before failure.
The Download Recording option is only displayed on the Jobs window if you have View permissions on Execution Media.
Updated 18 days ago