Set run options
To configure the settings for a specific Business Process (BP) run, navigate to the Run page of the BP instance you want to run.

Run page options
On the Run page, the following capabilities are available:
The Actions menu from where you can perform various actions with the BP run, such as copy, delete, or export it.
The Save button to save the BP run.
The Business Process flow scheme that you can view in full size by double-clicking it.
The Process Details section from where you can download the input data file for the BP run or see the number of process records.
The Advanced Options button to configure the settings for the BP run.
The Run This Process button to run the BP in the development or production environment.
Advanced Business Process settings
Click Advanced Options to open the page for setting BP run options. On the page, available BP run settings are arranged on the two tabs:
Global Variables: for details, read the Manage global variables topic.

Properties where you can configure the following settings:

Due date: set the date and time or period until which the tasks in the BP are to be completed. The BP tasks become unavailable after the specified due date and time or period.
Forcefully complete tasks: when enabled, the feature allows you to forcefully complete individual tasks and Business Processes when completion criteria are reached. The criteria are the percentage of task completion and idle time. A task is completed when both specified conditions are met.
Streaming between the steps configuration: set the minimum completion percentage required for streaming between the steps. Streaming is a mechanism for limiting the number of Records available in a BP step, depending on the number of Records completed in the previous one or more steps.
For example, let's assume the setting is 5. For the second BP step, it means that five Records must be completed on the first BP step before those are routed to the second one.
Streaming defines only the lower limit, meaning if 12 records are completed on the first step, they are routed to the second step all at once.
Try to repair failed tasks up to: specify the number of bot step execution retries for each Record in the BP.
If a bot step fails during execution (external server not available, RPA node disconnected, and so on), the step is automatically restarted until it is executed successfully or the retry limit is reached.
Afterwards, you can repair failed tasks manually. See View logs and repair Business Processes | Repair Business Process.
Custom attributes: select an underlying Field Scheme to set up custom attributes you want to add to the BP.
Track if transactions meet service level agreement (SLA): enabling this feature to track Service Level Agreement metrics.
To set the BP run options, configure any or all of the above settings and click the Save button. Once you are done with the configuration, you can proceed to run the BP.