This is fixed now. It was due to a bug (overflow) in the routine calculating the distance to other nodes. As the boundary in fact includes node several ten miles outside the working area this overflow happened and any node moved was joined with one of the boundary nodes. Thanks again for reporting this. The fix will be included in the next release.