Some trial and error showed me the way to remove the gap, is to set the same altitude restriction on both waypoints. As soon as there is any difference, this gap is introduced.

In Europe, there are quite a lot of examples where the published altitude restriction on the same waypoint, when in the START and when in the approach, is different. I know that doesn't make a lot of sense, but there you go. As a result of that, a gap is always introduced and can only be removed by tweaking the restrictions manually.

Although I understand the logic behind this heuristic, I believe this is non optimal behaviour, as an unconnectable gap means you need to remember to manually sequence to the second instance of that waypoint when on the leg to the first instance, without any warning or prompt to say this is required.

A better choice would be not to introduce this gap in the first place, or at least have some logic that forced the pilot to acknowledge or act on the gap.

Can this be considered for an upcoming release?