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?
In the case of a business exception, the transaction is not retried because business exceptions typically require human intervention. The Robotic Enterprise Framework is designed to treat business exceptions differently from system exceptions, meaning even if the Orchestrator queue retry settings are configured to allow retries, they won't apply to business exceptions. As a result, the transaction will not be retried.
In case of a business exception, the transaction is not automatically retried, since the issues related to business usually require human intervention
There are no retries for transactions that throw business exception
A makes no sense, the Orchestrator Queue in this section has the number of retries set to 2. The config file has it set to one time. Orchestrator's retry takes dominance over the config file if they values are not the same. So if the transaction item throws a business exception, it will be retried twice and if it doesn't work either time, the set transaction status workflow will be invoked and make the queue item status: Failed.
When the transaction encounters a business exception, it won't be retried regardless of whether or not Orchestrator queues are used.
A is the correct one
I thought about it some more analyzed the template. C is indeed correct. If it doesn't meet the business requirements, it makes no sense for the entry to be retried, process will simply move on to the next transaction item if any.
A is the correct one