How does "Retry on Configured Errors" work in Maestro?

Help Maestro
1

Hi everyone,

I’m trying to understand how Retry on Configured Errors works in Maestro.

In the task properties, the Retry Policy provides two options:

However, I couldn’t find documentation explaining what Configured errors actually refers to.

My questions are:

  1. What exactly are Configured errors?
  2. Where are they configured?
  3. Which task or process configuration does Retry on Configured Errors use to determine whether an error should be retried?

I’d appreciate any documentation or examples that explain this behavior.

Thank you!

2

@rashmisingh2695

Configured errors are defined and managed at the Process Level

Please check below documentation,

3
  1. Retry on All Errors → Retries the task for any failure.
  2. Retry on Configured Errors → Retries only for errors that are explicitly marked/configured as retryable in the task or process error-handling configuration.
  3. These retryable errors are typically defined by the workflow/process designer and are intended for transient issues (e.g., temporary connectivity or timeout errors).
  4. If no retryable errors are configured, the task may not retry when this option is selected.
4

I have created an RPA workflow and defined a few exceptions. In the task, I have enabled the retry policy and set it to retry on configured errors, but the process is not getting retried when the RPA workflow throws any error. If I select retry on all errors, it gets retried. Can you share any examples or guide me on where I can explicitly set or mark an exception for retrying?

6

Hello, for retrying on configured errors to work, you need to configure error handling (located in the section above retry config - where you can configure errors to be thrown upon certain conditions that you define:

Screenshot 2026-07-20 at 9.47.24 AM
Screenshot 2026-07-20 at 9.47.24 AM399×844 26.7 KB

7

I tried defining the error in the Conditional Throw section. When I run the process and the defined error condition is matched, the process execution stops instead of retrying.

Also, the documentation mentions that when a configured error matches, the error is propagated to the configured handler/node. Based on that, I’m not sure when Retry on configured errors actually comes into play.

image
image868×307 34.4 KB

Could you share a working example that demonstrates how to configure Retry on configured errors, including where the error should be defined and how the retry is triggered?