This makes the execution tree inconsistent. Following operations like deletion and migration can fail or produce undesired results.

Test case: https://github.com/camunda/camunda-bpm-platform/commit/2b939092769282f281d1d8d8b206ddb199abbcd7

Reason:

• This is the code that deletes the topmost scope in the execution hierarchy: https://github.com/camunda/camunda-bpm-platform/blob/7.8.0/engine/src/main/java/org/camunda/bpm/engine/impl/cmd/ModifyProcessInstanceCmd.java#L140-L150
• It does not consider any concurrent parent executions
• Must clean up concurrent parent executions as well, as is already implemented for cancellation instructions, cf https://github.com/camunda/camunda-bpm-platform/blob/7.8.0/engine/src/main/java/org/camunda/bpm/engine/impl/cmd/AbstractInstanceCancellationCmd.java#L58