RetryScope

This activity assists the user in executing a defined set of activities, considering the number of retry attempts and a specific interval, until either the specified condition is met, or an error occurs.

Properties

INPUT

NumberOfRetries: It indicates to provide the number of retries if the activities inside the “Body” has thrown exception or condition not satisfied. You can also either hardcode the path in a “Integer” datatype variable or manually enter the value in “Integer” type.
This field accepts values in “Integer” datatype.

RetryIntervalseconds: It assists the user in adding a delay after each number of retry  specified in starting the execution of the activities.
The delay duration here is in milliseconds. By default, it is set to “0” milliseconds.
When the option is left blank, the delay will not be considered.
You can also either hardcode the path in a “Integer” datatype variable or manually enter the value in “Integer” type. This field accepts values in “Integer” datatype.

Body: Gets auto filled once the “Activity” is dropped into the body.

MISC

DisplayName: Displays the name of the activity. The activity name can be customized, which aids in troubleshooting.

SkipOnError: Specify the “Boolean” value as “True” or “False.”
True: Continue executing the workflow regardless of any errors thrown.
False: Halt the workflow if it encounters any errors.
None: If the option is left blank, the activity will, by default, behave as if “False” were chosen.

Version: It indicates the version of the feature being used.

Example

Here’s an example of how the “ReTryScope” activity works in the workflow –

1. Create a solution for building a workflow.
2. Drag and drop the ”ReTryScope ” activity onto the designer pane and set it as the “Start Node.”
3. Navigating to the properties to provide the details.
a. Here in the “NumberOfRetries” property, I have provided the value as “3” so that the set of activities will be executed three times if the element does not exist.
b. Moving to the “RetryIntervalSeconds” property, providing the value as “10” to add a delay between each set of retry.
4. Now, placing the “ElementExist” activity from the “WebAutomation” feature.
a. Double-click the activity.
b. Here I am choosing the “Select Element” option.
c. Navigate to the webpage which I have already launched on my desktop.
d. Once you have chosen the “Element,” the attributes will be stored in the “Spy” window, along with an “image” of the element.
e. If you wish to add or remove any attributes, you can edit the “Attributes Editor.” In this case, we are not making any changes in the “Editor.”
f. Once you click on the “Save” button, the elements will be stored in the activity window.
5. Moving to the “ExistStatus” property in the output section to declare a variable to check if the element exists.
6. There are two methods to store the status in the variable.
7. Method 1: Double-click on the variable parameter in the “Output” section and enter a name that helps you easily identify it in the flow. Here, I’m using the name “Status” and using the shortcut key “Ctrl+Q” to create the variable.
8. Now, execute the workflow to view the results.