A data dependency between Activities A and B, e.g., through an IORules specification in B referring to data produced by A, results in compensation of B to be performed before compensation of A.

If A and B are two Activities that were active as part of an Ad-Hoc Sub-Process, then compensation of B MUST be performed before compensation of A if A completed before B started.

Instances of a loop or sequential multi-instance are compensated in reverse order of their forward completion. Instances of a parallel multi-instance can be compensated in parallel.

If a Sub-Process A has a boundary Event connected to Activity B, then compensation of B MUST be performed before compensation of A if that particular Event occurred. This also applies to multi-instances and loops.

13.5.6 End Events

Process level end events

For a “terminate” End Event, the Process is abnormally terminated—no other ongoing Process instances are affected.

For all other End Events, the behavior associated with the Event type is performed, e.g., the associated Message is sent for a Message End Event, the associated signal is sent for a Signal End Event, and so on. The Process instance is then completed, if and only if the following two conditions hold:

All start nodes of the Process have been visited. More precisely, all Start Events have been triggered, and for all starting Event-Based Gateways, one of the associated Events has been triggered.

There is no token remaining within the Process instance.

For a “cancel” End Event, the Sub-Process is abnormally terminated and the associated transaction is aborted. Control leaves the Sub-Process through a cancel intermediate boundary Event.

For all other End Events, the behavior associated with the Event type is performed, e.g., the associated Message is sent for a Message End Event, the associated signal is sent for a signal End Event, and so on. The Sub-Process instance is then completed, if and only if the following two conditions hold:

All start nodes of the Sub-Process have been visited. More precisely, all Start Events have been triggered, and for all starting Event-Based Gateways, one of the associated Events has been triggered.

There is no token remaining within the Sub-Process instance.