How many times will the transaction be retried?

A developer implemented a process using the Robotic Enterprise Framework and an Orchestrator queue. The MaxRetryNumber from the "Config.xlsx" file is set to "1" and the Max # of retries from the Queue settings from Orchestrator is set to "2". At runtime, the first transaction item throws a Business Exception.

How many times will the transaction be retried?
A . The transaction will be retried only one time.
B . The transaction will not be retried.
C . The transaction will be retried 2 times.
D . The transaction will be retried multiple times, until it will be processed successfully.

View Answer

Answer: B

Explanation:

The Robotic Enterprise Framework (REF) is a template that provides a structured and consistent way to develop automation processes. The REF uses an Orchestrator queue to store and process the transaction items, which are the units of work for the process. The REF also handles different types of exceptions that may occur during the execution of the process, such as system exceptions and business exceptions. A system exception is an error that prevents the normal execution of the process, such as a network failure or an application crash. A business exception is an error that is related to the business logic or rules of the process, such as an invalid input or an incorrect output.

The REF has different mechanisms to deal with these exceptions, such as retrying, logging, and updating the status of the transaction items.

The MaxRetryNumber from the “Config.xlsx” file is a parameter that specifies how many times the REF will retry a transaction item when a system exception occurs. The Max # of retries from the Queue settings from Orchestrator is a parameter that specifies how many times Orchestrator will retry a transaction item when it changes to Failed status due to any exception. These two parameters are independent of each other and have different effects on the retry mechanism.

In this case, the first transaction item throws a business exception, which means that there is something wrong with the data or the logic of the process. The REF will not retry a transaction item when a business exception occurs, because it assumes that retrying will not solve the problem.

Instead, the REF will log the exception, update the status of the transaction item to Failed, and move on to the next transaction item. Orchestrator will also not retry a transaction item when it changes to Failed status due to a business exception, because it respects the decision of the REF. Therefore, the transaction will not be retried at all.

References:

1: Robotic Enterprise Framework Template – UiPath Studio.