Association direction is lost when manually reconnecting a compensation task

[MaxTru]

Describe the Bug

When an association between a compensation boundary event is deleted and then manually added again, the association direction is lost. Also the preview of the association is incorrect:

The correct association is stored as:
<bpmn:association id="Association_1hyw3ph" associationDirection="One" sourceRef="Event_0qnefpa" targetRef="Compensation2Task" />

The incorrect association is stored as:
<bpmn:association id="Association_1sh64l5" sourceRef="Event_0xur0v7" targetRef="CompensationTask" />

Steps to Reproduce

1. Delete the association between a compensation boundary event and the respective compensation task
2. Manually re-add the association

Expected Behavior

• When manually readding the association, the associationDirection is set correctly
• When manually readding the association, the association preview matches the actual association

Environment

Tested on:

• OS: Arch Linux
• Browser: Chromium 81
• Library version: 7.2.0

And

• OS: Arch Linux, Modeler 4.0.0

[philippfromme]

So far I have found out that deactivating the connection preview feature fixes the issue. The bug seems to be caused by the connection preview.

[Skaiir]

Dragging the association twice fixes this which is interesting

[nikku]

Fixed with bpmn-js@16.3.0.