订阅

UiPath Orchestrator

UiPath Orchestrator 指南

管理作业

开始作业


Before going through the steps below, you need to create a process.

  1. Navigate to Automations > Jobs from the folder that the process resides in.
  2. 单击“开始”。系统将显示“开始作业”窗口。
  3. 从“流程名称”下拉列表中,选择一个先前已部署到当前文件夹的进程。
  4. Configure the required fields, as follows:
  5. 单击“开始”。关闭“开始作业”窗口,如果当前处于活动状态的文件夹中有可用的运行时,则根据您所做的设置在机器人上启动作业。作业的状态实时显示在“作业”页面上。

Setting the job priority

From the Jobs Priority drop-down, select the priority of the job to be executed, if you want it to be different from the priority set at the process level. This field is automatically populated with the priority inherited from the package.

Selecting the execution runtime

从“运行时许可证”下拉列表中,选择用于执行作业的运行时类型。下拉列表下方会显示可用和已连接的运行时数量。

  • “_ 可用” - 可用的运行时数量,以运行时总数减去正在运行的作业数计算得出。
  • “_ 已连接”- 运行时总数,以连接到与活动文件夹关联的 Orchestrator 的所有计算机上的运行时总和计算得出。
Runtime licenseDescription
UnattendedThe job is executed in unattended mode consuming an Unattended runtime.
NonProductionThe job is executed in unattended mode consuming a NonProduction runtime.
TestingThe job is executed in unattended mode consuming a Testing runtime.
DevelopmentThe job is executed in unattended mode using a Development runtime. This allows developers to run jobs from Orchestrator in their personal workspace, for testing and debugging purposes, without consuming an Unattended, NonProduction or Testing license. See details about debugging using personal workspaces.

示例:假设计算机模板 A 有 2 个非生产运行时和 1 个无人值守运行时,计算机模板 B 有 3 个非生产运行时和 2 个无人值守运行时。两个模板都与一个文件夹相关联。在每个模板上,您连接一台主机。产生的运行时状态如下:

  • 无人值守:3 Available, 3 Connected
  • 非生产:5 Available, 5 Connected

占用一个运行时的正在运行的作业会从该类型的可用运行时数中减去 1。

Configuring the execution target

Configure your execution target by setting the options below as desired on the Execution Target tab.

12381238

动态分配

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 次。

帐户

You can choose one of these approaches:

  • 指定帐户意味着系统将在该特定用户或机器人帐户下执行流程。
  • Specifying both the account and the machine means the job launches on that very account-machine pair. Only valid account-machine pairs are available for selection.
  • 如果未指定帐户,则 Orchestrator 会动态分配帐户。

计算机

You can choose one of these approaches:

  • Specifying a machine object means the process is executed on one of the host machines attached to the selected machine template. Select a specific host machine from the pool of connected host machines on the Connected Machines field.
  • Specifying both the account and the machine means the job launches on that very account-machine pair. Only valid account-machine pairs are available for selection.
  • 如果未指定计算机,则 Orchestrator 会动态分配主机。

确保将与作业类型匹配的运行时分配给关联的计算机模型。仅显示与活动文件夹关联的已连接主机。

Keep Account/Machine allocation on job resumption

此字段可用于配置是否在相同的帐户-计算机对上执行长时间运行的作业的不同片段。
By default, a suspended job is resumed on any available robot on any available machine.
Based on your license or resource requirements, you have the option to resume a job on the same machine and in the same account context that started the job.

假设您需要 SAP 许可证才能执行作业。您可以在单台计算机上安装 SAP 许可证,并使用该计算机来启动和继续作业,而不必在每台可用的计算机上安装 SAP 许可证(这样会增加成本)。相同的策略可能适用于用户许可证。您只能分配一个用户许可证,并使用它来执行作业。

Scheduling the end of job execution

Schedule ending of job execution

The process execution may sometimes be faulty, causing the job to remain in the pending state. Turning on the toggle allows you to (click to expand):

  • Select Stop from the drop-down menu - this attempts to gracefully end the execution after the defined time interval has passed since the job is stuck in a pending state (set the time to a minimum of 1 minute, maximum of 10 days, 23 hours and 59 minutes).
  • Select Kill from the drop-down menu - this attempts to forcefully end the execution after the defined time interval has passed since the job is stuck in a pending state (set the time to a minimum of 1 minute, maximum of 10 days, 23 hours and 59 minutes).
  • Select Stop from the drop-down menu and turn on the Schedule automatic "Kill", if the job does not stop option - this attempts to gracefully end the execution after the defined time interval has passed since the job is stuck in a pending state and then attempts to forcefully end it after the defined time interval has passed since the job is stuck in a stopping state (set the time to a minimum of 1 minute, maximum of 10 days, 23 hours and 59 minutes).

Generating alerts

Generate an alert if the job is stuck in pending or resumed status

By turning on the toggle, you activate alerts about jobs that remain in the pending or resumed status longer than the specified duration.
The configurable duration is minimum one minute and maximum eleven days.
If the job exceeds the configured duration, an "Error" severity alert pop-up informs you about it with the following text:
"N jobs for #process {process_number} have been pending or resumed for more than X hours and Y minutes.", where:

  • N - is the number of jobs that triggered the alert
  • {process_number} - the process identifier
  • X - the configured number of hours the job exceeded while having the pending or resumed status.
    Note: Days are converted to hours.
  • Y - the configured number of minutes the job exceeded while having the pending or resumed status.

Generate an alert if the job started and has not completed

By turning on the toggle, you activate alerts about jobs that do not complete in the specified duration.
The configurable duration is minimum one minute and maximum eleven days.
If the job exceeds the configured duration, an "Error" severity alert pop-up informs you about it with the following text:
"Job for #process {process_number} has been pending been running for more than X hours and Y minutes.", where:

  • {process_number} - the process identifier
  • X - the configured number of hours the job exceeded while trying to complete.
    Note: Days are converted to hours.
  • Y - the configured number of minutes the job exceeded while trying to complete.

Orchestrator 会阻止使用无效配置启动作业。尝试在无效的设置中启动作业会导致显示描述性错误消息,为您提供有关如何修复配置的详细信息。

12521252

Starting a job using dynamic allocation, i.e. no machine or account specified, with an incompatible folder setup results in an error. Make sure to correct the setup, otherwise, jobs stay pending indefinitely. For example, trying to run a .NET Framework 4.6.1 background job when there are only cross-platform templates in the folder does not work, as jobs stay pending until the configuration is fixed.

Adding arguments

On the Arguments tab, provide input arguments for the selected process. This tab is automatically populated with all the input arguments accepted by the selected process, and the corresponding values inherited from the package.

停止作业


单击相应的“更多操作”按钮,然后单击“停止”。自动化项目将一直执行,直至找到“应停止”活动。在此期间,作业处于“正在停止”状态。如果遇到该活动,执行将停止,并且作业的最终状态为“成功”。如果未找到“应停止”活动,则作业执行在到达项目末尾时才会停止。在这情况下,最终状态也为“成功”

📘

注意

  • 从 Orchestrator 启动的作业只能从 Orchestrator 停止
  • 从 Assistant 启动的作业既可以从 Orchestrator 的“作业”页面停止,也可以使用 UiPath Assistant 停止
  • 作业被停止后,作业结束计划将丢失,您需要在重新启动作业时重新配置“计划结束作业执行”选项。

继续作业


单击相应的“更多操作”按钮,然后单击“继续”

终止作业


Click the corresponding More Actions button, and then Kill. The automation project is forcefully stopped, the job is marked as Stopped, and "Job canceled" is displayed in the Job Details window.

📘

注意

  • 从 Orchestrator 启动的作业既可以从 Orchestrator 的“作业”页面终止,也可以使用 UiPath Assistant 终止
  • 从 Assistant 启动的作业既可以从 Orchestrator 的“作业”页面终止,也可以使用 UiPath Assistant 终止
  • 作业被终止后,作业结束计划将丢失,您需要在重新启动作业时重新配置“计划结束作业执行”选项。

重新开始作业


此功能使您可以快速从作业列表运行作业,而无需完成作业配置流程。您可以重新开始任何处于最终状态(“已停止”、“发生故障”或“成功”)的作业。

📘

注意

  • 您无法重新启动由代理程序(例如 Assistant)或通过 Studio 远程调试会话触发的作业。
  • 当您重新启动已启用“计划结束作业执行”选项的作业时,您需要重新配置这些选项。

This procedure starts from the presumption that you previously started a job that already reached a final status.

  1. 单击相应的“更多操作”按钮,然后单击“重新启动”。系统将显示“开始作业”窗口,其中包含作业的初始设置。
  2. 进行所需的更改。
  3. 单击“开始”。系统会关闭“开始作业”窗口,然后开始执行。作业状态实时显示在“作业”页面上。

查看作业日志


要查看特定作业的日志,请单击相应的“更多操作”按钮,然后单击“查看日志”。系统将显示“日志”页面,其中包含有关指定作业的数据。

📘

注意

若作业通过远程调试会话启动,其生成的日志在“作业日志”页面上不可用。您可以在全局“日志”页面上找到它们。

查看作业详细信息


要查看有关特定作业的详细信息,请执行以下步骤:

  1. 单击相应的“查看详细信息”按钮。系统将显示“作业详细信息”窗口。在这里,您可以找到各种信息,例如基础流程的名称、执行的机器人和计算机、作业失败的原因等。
594594

📘

注意

“信息”字段不会显示关于失败的作业的许可证注意事项。请使用监控功能获取有关许可证的详细信息。

下载执行介质


To download the recording for a faulted job, click More Options > Download Recording. Execution media is downloaded according to your settings.

约一个月前更新


管理作业


建议的编辑仅限用于 API 参考页面

您只能建议对 Markdown 正文内容进行编辑,而不能建议对 API 规范进行编辑。