This problem occurs whenever there is more than one scoped compensation handler (e.g. a subprocess compensation handler, a default handler (where we descend into a scope)). The example diagrams show this with multi-instance but this is not multi-instance-specific.

Detailed description (example newDiagram_2.png):
When throwing compensation, the activity tree should look like this:

Process Definition
  ThrowCompensate
  SubProcess#MiBody
    SubProcess
      CompensationHandlerTask
    SubProcess
      CompensationHandlerTask
    SubProcess
      CompensationHandlerTask

but it looks like

Process Definition
  ThrowCompensate
  SubProcess#MiBody
    SubProcess
      CompensationHandlerTask
      CompensationHandlerTask
      CompensationHandlerTask

Reason: When throwing compensation, we don't create concurrent executions for the execution tree that is created as a child tree of the compensation-throwing execution. However, these are required for storing activity instance IDs in the cases described here.