Run from this Activity

Run from This Activity is a workflow execution option that allows users to start a workflow from a selected activity instead of executing the entire workflow from the beginning. This feature supports efficient development, testing, and debugging by enabling users to target and validate specific sections of a workflow without repeating previously completed steps.

How It Works

When a user selects an activity and triggers the Run from This Activity option, the workflow engine skips all preceding activities and begins execution from the selected point. The workflow then continues to execute sequentially from that activity onward until it either completes successfully or encounters an error.

a. The Run from This Activity option is available only for activities that are connected to a node within the workflow.
b. Activities that are not connected to any node will not have this option enabled and cannot be executed using this feature.

During execution, the Debug Watcher panel automatically opens and displays the variables, arguments, and properties of the currently executing activity.

Debug Watcher

The Debug Watcher is a dedicated debugging panel in Robility Designer that provides real-time visibility into the internal state of a workflow during a debug session. It allows users to monitor and inspect variables, arguments, and activity properties as the workflow executes step by step, making it an essential tool for identifying issues, validating logic, and ensuring the workflow behaves as expected.

Sections in Debug Watcher

1. Variables – Displays all variables defined in the workflow along with their current runtime values during execution.

Each entry includes:
a. Variable Name – The name of the variable. 
b. Variable Type – The data type of the variable, such as Boolean, String, or Int32.
c. Value – The current runtime value of the variable.
This section helps track how variable values change as activities are executed.

2. Arguments – Displays all arguments passed into or out of the workflow during execution.

Each entry includes:
a. Argument Name – The name of the argument.
b. Argument Type – The data type of the argument.
c. Value – The current runtime value of the argument.
This section is useful for debugging workflows that are invoked by other workflows and rely on input or output arguments.

3. Properties of the Selected Activity – Displays the input and output properties of the currently executing activity.

Each entry includes:
a. Property Name – The name of the property.
b. Property Type – Indicates whether the property is an input (InArgument) or output (OutArgument) and displays its data type.
c. Value – The current value assigned to the property.
This section helps verify that the correct values are being passed into and returned from each activity during execution.

Visual Indicators
During execution, Robility Designer provides real-time visual feedback to help users track workflow progress:
Yellow – Indicates the activity that is currently being executed.
Green – Indicates activities that have completed successfully.
This color-coded highlighting provides a clear visual trail of workflow execution, making it easier to monitor progress and identify the current execution state.

Key Benefits

1. Saves Time: Eliminates the need to rerun the entire workflow when only a specific section needs to be tested or validated.
2. Improves Debugging: Allows developers to isolate and focus on a particular activity or workflow section without interference from earlier steps.
3. Enhances Development Efficiency: Especially useful when working with large or complex workflows containing numerous activities.
4. Targeted Validation: Enables precise testing of specific automation logic without rerunning previously completed steps.

Important

Activities that depend on variables, application states, or outputs generated by earlier steps may require those dependencies to be available before execution. If the selected starting activity relies on data or conditions established by preceding activities, those prerequisites must be manually configured or ensured before triggering Run from This Activity. Failure to do so may result in errors or unexpected behavior.