Subscribe

UiPath Activities

The UiPath Activities Guide

Invoke Process

UiPath.Core.Activities.InvokeProcess

About the InvokeProcess activity

Executes a UiPath process that is available for the local machine. Can be used to run local packages, as well as processes in Orchestrator, if a connection is available.

For more information on how to find the list of available processes on a machine, go here

The Invoke Process activity runs in Synchronous mode, meaning that the parent process waits for the child process to complete before resuming.

Logs generated by the child processes only contain the outcome of the execution and errors, and are written in the same place as the ones from the parent and can be differentiated by the ProcessName field in local logs and Process column in Orchestrator.

When using the Invoke Process activity, even though the project contains multiple processes, a single job is created for running them as opposed to the Run Parallel Process activity which creates separate jobs for each process in the project.

๐Ÿ“˜

Note:

Unserializable data types cannot be passed between workflows (e.g. UIBrowser, UIElement, etc).

If a child process is invoked but not found, an error is logged containing the name of the child process, the path where Robot searched for it and additional details such as WindowsIdentity and machineName.

๐Ÿ“˜

Important!

When using a version of the UiPath.System.Activities that is higher than v20.4, Invoke Process supports multiple entry points. If a workflow is created with this version and then the UiPath.System.Activities pack is downgraded to an older version that only supports a single entry point, the Invoke Process activities in the workflow suffer validation errors and must be manually replaced to work.

๐Ÿ“˜

Important!

This activity is only compatible with Studio v19.6 and above.

Properties

Common

  • ContinueOnError - Specifies if the automation should continue even when the activity throws an error. This field only supports Boolean values (True, False). The default value is False. As a result, if the field is blank and an error is thrown, the execution of the project stops. If the value is set to True, the execution of the project continues regardless of any error.

๐Ÿ“˜

Note:

If this activity is included in Try Catch and the value of the ContinueOnError property is True, no error is caught when the project is executed.

  • DisplayName - The display name of the activity.
  • Timeout - Specifies the amount of time (in milliseconds) to wait for the activity to run before an error is thrown. Leaving this property empty waits for an infinite amount of time before throwing an exception. By default, this property field is empty.

Input

  • Arguments - A list of parameters that are passed to the invoked workflow at runtime.
  • Process Name - The name of the process that you want to run. This field supports only strings and String variables. Process Name should contain the name of the Package, as that is being used by the Robot.

Misc

  • Entry Point Workflow - The path of the workflow file that isrun at the start of the process, relative to the package root. If left empty, the default entry point is Main.xaml. This field supports only strings and String variables.
  • Orchestrator Folder Path - The path of the Orchestrator folder where the specified process is located, if different from the folder where the process is running. This field only supports string values, with / as the separator to indicate subfolders. For example "Finance/Accounts Payable".

๐Ÿ“˜

Note:

The Orchestrator Folder Path parameter does not work for processes executed by robots in classic folders. Only robots in modern folders have the ability to pass data outside of their folder.

  • Private - If selected, the values of variables and arguments are no longer logged at Verbose level.

Updated 28 days ago


Invoke Process


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.