Workflow activities

UiPath.Activities.System.Jobs.RunJob
UiPath.Activities.System.Jobs.RunJob

Description​

Project compatibility​

Windows, Cross-platform configuration​

• Activity body properties:

  • Orchestrator folder path—The Orchestrator folder where the automation you want to start is deployed. Only the folders you can access are displayed in the dropdown menu. The availability of this property depends on the context:
    • Outside a solution—The property is always available. If you do not select a folder, your Personal Workspace is used.
    • Inside a solution, Process name set to a solution resource—The property is visible but read-only and is not taken into account.
    • Inside a solution, Process name set to a variable—The property is available for you to select the target Orchestrator folder.
  • Process name—Select the process associated with the automation you want to run. All types of processes are displayed: RPA, Agents, Agentic Orchestration. If the process you need is not listed, select Manage processes to be redirected to your folder in Orchestrator, where you can add the missing process.
  • Input arguments—Configure the arguments to pass to the selected process. Three input modes are available via the icon next to the property:

    • Use Schema (default)—Auto-imports the process argument schema and generates a custom data type that is editable with the Data Mapper. The Output arguments property is shown separately. To retrieve the latest list of process arguments, select Refresh at the right side of the property.

      Important:

      For the best experience, make sure you are using the latest Studio version. Studio versions previous to 2025.0.161 use the Expression Editor window. The following code snippet shows you how to provide values to agent input arguments using VB.NET and C#:

      assignment

      'VB.NET
      New Email_Rewriter_Input() With {
      .feedback = "sample feedback",
      .originalEmail = "sample email content"
      }
      'VB.NET
      New Email_Rewriter_Input() With {
      .feedback = "sample feedback",
      .originalEmail = "sample email content"
      }
      

      assignment

      //C#
      new Email_Rewriter_Input {
      feedback = "sample feedback",
      originalEmail = "sample email content"
      }
      //C#
      new Email_Rewriter_Input {
      feedback = "sample feedback",
      originalEmail = "sample email content"
      }
      

    • Use Arguments—An Arguments widget where each entry has a Name, Value, and Direction (In/Out). Both input and output arguments are configured here. The Output arguments property is hidden in this mode — output values are received via entries with Direction set to Out.

    • Use Object—Accepts any variable or object expression as input, which is JSON-serialized at runtime and passed to the process. JSON strings are passed as they are. The Output arguments property is still shown separately.

• Properties panel:

  • Execution mode—Select how the activity waits for the job to complete. The following options are available:
    • Do not wait—The activity starts the job and allows the workflow to continue without waiting for the job to complete.
    • Wait for job completion—Default option. The activity pauses the workflow until the started job finishes or the timeout is reached. If the job completion is successful, the activity returns the outputs, and the workflow resumes.
      Note:

      This execution mode utilizes the Orchestrator SignalR capability to acknowledge job completion in real-time. It can be enabled in the Orchestrator Settings at the Tenant Level. If SignalR is disabled, this execution mode will default to 30-second polling.

    • Suspend execution until job completion—The activity pauses the workflow and awaits output with persistence.
  • Timeout—Sets the maximum time to wait for job completion. Default value is 600,000 milliseconds (10 minutes).
  • Continue on error—Specifies whether 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 not configured 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.
  • Fail when job fails—This property becomes available only when the execution mode is Wait for job completion or Suspend execution until job completion. Specifies whether the activity should throw an exception when the executed Orchestrator job completes with a Faulted status. The default value is Off. Set to On to throw an exception and stop the execution of the workflow when the Orchestrator job fails.
  • Job data—Displays the object of the started job. Generated automatically.
  • Output arguments—Displays the output arguments returned by the process upon completion. This property is only shown when using Use Schema or Use Object input mode. When using Use Arguments mode, output arguments are captured via entries with Direction set to Out in the Arguments widget. If you select the process from a process list, the output object contains all the output properties of the selected process. If you provide the process using an expression and the process returns values, you must configure input and output arguments using the Use Arguments option.

Known limitation​

• The Run Job activity does not detect the failure.
• When configured to Wait for job completion, it either:
  • Times out, or
  • Hangs indefinitely in persistence mode, since the job never reaches Successful.

• For Wait for job completion, apply a Timeout that matches the expected duration of the Agentic Process. Without it, the workflow remains stuck, waiting for a job status change that never occurs.
• Use Suspend execution until job completion, as this mode works best when your workflow needs to receive outputs. The process resumes automatically when the Agentic Process completes.