A process uses the Robotic Enterprise (RE) Framework without access to Orchestrator. Based on best practices, what is the recommended way to ensure a transaction will be retried in the event of an Application Exception while processing that transaction?
To ensure that a transaction will be retried in the event of an Application Exception while using the Robotic Enterprise (RE) Framework without access to Orchestrator, it is recommended to set the MaxRetryNumber in the Config.xlsx file to a number greater than 0. This configuration setting dictates the number of times a transaction should be retried before it is marked as failed, thereby providing an effective way to handle retries for application exceptions.
MaxRetryNumbe is for System Exception.
isnt application exception and system exception similar?
Sorry the correct answer is C !
MaxRetryNumber in Config -- Must be 0 if working with Orchestrator queues. If > 0, the robot will retry the same transaction which failed with a system exception. Must be an integer value.
Correct answer is C, open config file and read definition of MaxRetryNumber in constants sheet
Option B is correct
C. Set the MaxRetryNumber in the Config.xlsx file to a number greater than 0
Correct answer is C, open config file and read definition of MaxRetryNumber in constants sheet