RetryScope

Estimated reading: 3 minutes

The Retry Scope activity is used to repeatedly execute an action until a defined condition is met or the maximum number of retries is reached. It is commonly used to handle temporary failures such as slow web page loading, delayed UI elements, or intermittent system responses, ensuring that the automation workflow continues reliably without manual intervention.

Properties

INPUT

NumberOfRetries*: Specifies how many times the activity should be retried if the condition is not met. Accepts an Integer value. The value can be hardcoded or passed dynamically through a variable.

RetryIntervalSeconds*: Specifies the wait time between each retry. Accepts an Integer value in seconds. The value can be hardcoded or passed dynamically through a variable. The default value is 0, meaning no delay between retries.

MISC

Body: Auto-populated when an activity is added to the Action.
Displays Sequence if multiple activities are used.
Displays the activity name if only a single activity is used.

Condition: Auto-populated when an activity is added to the Condition.
Displays Sequence if multiple activities are used.
Displays the activity name if only a single activity is used.

DisplayName: Specifies the name of the activity. This can be customized to aid in troubleshooting.

SkipOnError: Specifies a Boolean value (True or False):
True: Continues executing the workflow regardless of errors.
False: Stops the workflow if an error occurs.
If left blank, it behaves as False by default.

Version: Indicates the version of the feature being used.

OUTPUT

Condition: Returns a Boolean value that indicates whether the condition was satisfied after execution:
True: The condition is met (Retry Scope stops successfully).
False: The condition is not met (Retry Scope continues retrying until limit is reached).

How Retry Scope Works

On the screen canvas, the Retry Scope is divided into two sections: Action and Condition.

Process Table

Component	What it Means	How it Works
Action	The step where the system performs a task such as clicking a button, opening a page, or entering data. These tasks may fail temporarily due to delays or unavailable elements.	Runs at least once. If it fails or does not meet the required condition, it is retried after a short delay. This continues until it succeeds or the retry limit is reached.
Condition	A True/False check that confirms whether the Action was completed successfully.	After each attempt, the condition is evaluated. If True, the process stops successfully. If False, the Action is retried after the defined delay until success or maximum retries are reached.

Example: Retry Scope Usage

This example shows how Retry Scope can automatically retry by clicking a button on a web page until a success message appears, ensuring the process works even if the page is slow or unresponsive.

1. Add the Retry Scope activity to a new workflow and set NumberOfRetries = 3 and RetryIntervalSeconds = 10 (wait 10 seconds between retries).

2. In the Action section, add a Click activity and select the target button using Indicate on Screen.

3. In the Condition section, add an Element Exists activity and select the message element. It returns True when the element is found (success) and False when it is not (retry required).

4. The workflow clicks the button, checks the condition after each attempt, retries if the result is False, and continues once the condition becomes True or stops after reaching the maximum retries.

RetryScope

Properties

How Retry Scope Works

RetryScope

CONTENTS