Wrong catch block when throwing BussinesRuleException

[LukJas]

Hi,

I just realized that the catch order isn’t the same as in .NET.
Have a look at the following picture:
I would have expected, that the Exception-cach block would trigger, because its the first one on the top. Instead the BussinesRuleException-catch block was entered.
Is this the normal behavior?

[anil5 (Anil Kumar Bandam)]

Hi,

It’s the normal behaviour the catch block catches the specific type of exception first and as you mentioned in throw activity as business exception that’s why the business exception of catch block is executed. First.

In try activity try to generate other than business exception, then it will execute the first block in catch that is system exception.

[andrzej.kniola (Andrzej Knioła)]

Not strictly related, but if you were surprised by catch order then this is also a must read:

Try-Catch Finally improvement

Finally block should be executed always, no matter if exceptions were raised or not and if exceptions were caught or not. Today, in 2017.1 SP1, if the exception is not caught or if the exception is caught and then rethrown, the finally block is not executed. Actually, today’s behaviour is like having the activities in the Finally block outside/after of the Try-Catch activity.