Retry

Retry

Type: retry  ·  Package: Core Activities v1.0.0

Runs a block of activities, and if fails, retries** up to a maximum number of times, with an optional wait between attempts. It is ideal for actions that fail intermittently and that usually work on the second or third attempt: a slow web page, an unstable network, a system that is slow to respond.

How it works

1. Execute the body block.
2. If successful, it terminates and continues the flow.
3. If it fails, log a warning with the reason, wait delay milliseconds (if you configured it), and try again.
4. Repeat until attempts attempts are exhausted. If all fail, the activity fails with the last error (which stops execution unless inside a Try / Catch).

Required parameters

Parameter	Editor	Description
attempts	expression	Maximum number of attempts, including the first. Ex: 3 = one attempt + 2 retries.

Optional parameters

Parameter	Editor	Description
delay	expression	Milliseconds to wait between attempts. By default 0 (no wait).

Subflows (lanes)

body requerido

The activities to execute and, if they fail, retry.

Example

Retry a web action up to 3 times, waiting 2 seconds between attempts:

Retry   attempts = 3   delay = 2000
 └─ body:
      Page Navigate   page = = pagina   url = "https://erp.cliente.com"
      Page Click      page = = pagina   selector = "#login"

If the first attempt fails (page did not load), wait 2 s and try again; If the second one fails, wait and try again. If the third also fails, the activity fails with the last error.

Each attempt reruns the ENTIRE body

If the block has multiple activities and the last one fails, retry reruns all from the beginning. Keep in body only those actions that make sense to repeat together (ideally idempotent — repeating them won’t cause duplicate effects).

Retry vs Delay vs Try/Catch

• Delay: Fixed wait, no retry. Fragile on its own.
• Retry: Retry an unstable action. The best option for transient failures.
• Try / Catch: Handle the error with a plan B when retrying is not enough.

Combine them: put a Retry inside the try of a Try/Catch to retry first and handle the final failure later.

Related activities

• Try / Catch — handle error if all attempts fail.
• Delay — espera fija (Retry ya incluye delay entre intentos).