Reproduce:

• Given the following process: ... --> serviceTask A --> userTask B --> ...
• B has 1 token
• Use Cockpit to move token B to A
• Apply Modification

Expected behavior:

• A gets executed, token is again at B after modification

Observed behavior:

• A gets executed, then token is destroyed after reaching B

Reason:

• Cockpit does a cancel all for source activity, killing the newly created token

Proposed solution:

• Explicitly state the task instances which should be canceled
• Furthermore it should be possible to explicitly select the instance if manually cancelling a task with a single instance (if you recreate the scenario without token move)