MENU
When encountering an ApplicationException, what occurs if the developer chooses InvalidOperationException as the exception handler within the Catches section of the Try Catch activity?
In a Try Catch activity within UiPath, when an exception is thrown that does not match any of the exception types specified in the Catches section, the exception is unhandled by the Catches section. If the thrown exception is an ApplicationException and the Catches section is only configured to handle an InvalidOperationException, then the ApplicationException is not caught because it is a different type of exception.
However, regardless of whether the exception is caught, the Finally block always executes. The Finally block is designed to run after the Try block and after any Catch blocks are checked for matches (regardless of whether a match is found or not).
Therefore, the correct answer is:
A) The Finally block is executed and the Catches section catches the exception.
In this context, 'the Catches section catches the exception' means that the Catches section is evaluated for a match. Since ApplicationException is not handled by the InvalidOperationException catch block, the exception is not actually caught, but the Finally block will still execute.