Study the following process flow on the Main Page of a process where the intention is to preserve the current exception.
What is wrong with the design?
Study the following process flow on the Main Page of a process where the intention is to preserve the current exception.
What is wrong with the design?
B is the correct answer
I tested this simulation and found that it falls into an infinite loop because the "Re-throw" exception is caught by the "Recover2", which leads to "Re-throw" again and again. I think the correct answer is A. (furthermore, with the exception block added, then RPA is correct that the exception is preserved)
A is correct. It will create an infinite loop with Recover2 catching the exception over an over again. B is incorrect as the exception stage can be configured to preserve the exception type and detail of the original exception even after a resume stage.
The exception will be preserved, I've seen that the current exception is still available even after the Resume stage.
The correct response is: B. The exception caught by Recover2 will not be preserved by the Re-Throw Exception stage Explanation: The provided flow includes two Recover stages (Recover1 and Recover2) and a Re-Throw Exception stage. The issue is that the exception caught by Recover2 will not be preserved by the Re-Throw Exception stage. In Blue Prism, a Re-Throw Exception stage can only re-throw exceptions caught by the nearest preceding Recover stage. In this case, the Re-Throw Exception stage is located after Recover1, so it can only re-throw exceptions caught by Recover1. The Re-Throw Exception stage does not have the capability to preserve and re-throw exceptions from multiple Recover stages. If there is a need to preserve exceptions caught by multiple Recover stages, an alternative approach might be needed, such as handling the exceptions at a higher level or passing exception-related information through outputs or data items.
B is the correct answer, because to preserve the exception from recover stage the exception stage should be immediately after recover stage, here there is resume action and resume stages are there in between. "Resume stage will be used to eliminate the exception" REF: https://blue-prism.docebosaas.com/learn/course/19700/play/43334:834/blue-prism-advanced-exception-handling;lp=230
REF: https://blue-prism.docebosaas.com/learn/course/19700/play/43334:834/blue-prism-advanced-exception-handling;lp=230
B is the correct answer, because to preserve the exception from recover stage the exception stage should be immediately after recover stage, here there is resume action and resume stages are there in between
Correct option is B , as after resume stage exception will be diffused.
I think it is A
Infinite loop as there is no block limit catching error
B is correct as you have passed the resume the stage and the Exception is no longer in scope.
Yes, B is the correct answer.
A and B. [A] because if the recover is not in block the code stage error will again be caught and end in infinite loop. [B] because there is a resume stage. It should be removed to preserve exception.
https://chercher.tech/blue-prism-certification/blue-prism-certified-developer-mock-test-set-3
B is the correct answer as exception details will be lost after the resume stage.
The answer is A. Once you wrap the exception in a block it preserves the exception