Non-persistent Message flow connector
A messageflow connector connects two lanes.
When opening the BPM file, the message flow connector is not connected anymore. (see attached Situation 1,2 and 3). After re-connecting, the validation says everything is fine. See Situation 4.
The BPM is saved.
After reopening the BPM the non-connection starts again (Situation 1). This issue can be repeated.
I attach the Situation pictures and the BPM to test.
What to do ....?
The version we work with is 3.1.0.011, 64bits.