Yes, that is an unfortunate behavior of the new TRY-CATCH construct. As a result, some of us have opted to stick with the traditional SEQUENCE-based try-catch. I think that may be your best bet as well. Here’s a thread where this issue was discussed a bit: