With active compensation (perhaps even hierarchical, i.e. nested subprocesses where an inner subprocess has a compensation handler), the execution tree contains concurrent + scope execution (the former event scope executions). The deletion logic can't deal with this at the moment.

Impact:

• things like undeployment or deletion via API may fail
• appears only when the comensation throw event is executed concurrently (i.e. it is executed by a concurrent, non-scope execution)