Compensation activities

When a compensation is triggered, a token at a compensation activity immediatley enters the respective compensation activity and receives ENTERED state. It changes its state according to the reduced state diagram below and as described in Subprocesses and ad-hoc subprocesses or Tasks. Feasibility is checked directly after COMPLETED state without waiting for an exit decision. When a token has feasibly completed, the token is disposed without further. Otherwise, a failure is raised.

stateDiagram-v2
    state feasibleEntry <<choice>>
    state feasibleCompletion <<choice>>
    [*] --> ENTERED
    ENTERED --> feasibleEntry
    feasibleEntry --> BUSY: [feasible]
    feasibleEntry --> FAILED: [infeasible]
    BUSY --> COMPLETED
    BUSY --> FAILED: failure
    COMPLETED --> feasibleCompletion
    feasibleCompletion --> [*]: [feasible]
    feasibleCompletion --> FAILED: [infeasible]
    FAILED --> [*]

Note

A compensation activity can not be compensated.