[Discussion] Is it an exception bug in BP? or just wrong use of Blocks and why?

[Anonymous]

Dear All,  I was testing exception cases and I was expecting this scenario to get terminated because of nested exceptions. But what happened is after the second exception (nested exception happened) process returned to recovery 1.   Note1: Calc1 is dividing by zero.  Note2: I'm not looking for a solution for this structure. I just want to know the reason/logic lead returning to recover 1 instead of termination of the process.  SS is attached.  

[Denis__Dennehy]

I am not sure of the answer to this.  Once you have finished your Blue Prism training (foundation plus all the mandatory modules) the only thing you need to do is use the standard process templates as the basis of all your process builds and use the exception handling within that - it just works. 

[DavidEdwards-Da]

Of course the process returned to Recovery1, you have a recovery stage that's not contained within a block so it catches exceptions that occur in stages outside of a block (with it's own matching recovery stage)

[DavidEdwards-Da]

Scratch that  - I'm an idiot who didn't read the nested exceptions part properly 😛

[Anonymous]

@Denis__Dennehy @DavidED Thank you for your reply I finished the training yes. I think you understood me wrong. My question is, according to BP exception handling document internal exceptions will cause termination of the process. And in the attached screenshot you can see that in recovery mode one another exception will occur because am dividing by zero so this is a nested exception right? so it should terminate but what happened is, recovery one which is outside the block catch the nested exception and the process will keep looping.  If you have free time try doing this process in BP and I think you'll get the point of my question. Thank you.