BPMN2 — Page 203, Table 10-26, MultiInstance Activity: What is the intended use case if the catching boudnary event is interrupt

Page 203, Table 10-26, multiInstanceLoopCharacteristics: I believe that the motivation behind having events thrown in coordination with the completion of instances of multiInatnce activity is to have non-interrupting boundary events to carry out some desired ackownledgements (or other defined activites), but if the catching boudnary event is interrupting, the alternate flow will be followed potentially resulting in un-expected or suspected behavior.

What is the intended use case if the catching boudnary event is interrupting?

The design of the MI activity was done with the use case in mind that the catching boundary event is non-interrupting.
However, we do not see a strong reason to rule out that the catching boundary event could be interrupting.
Disposition: Closed, No Change