Here's your previous post, Michel:
https://www.wikitree.com/g2g/1553137/merge-into-other-lnab-order-not-respected
And another example https://www.wikitree.com/index.php?title=Moes-224&diff=187824256&oldid=182971107
The problem here is people are not reading the comments to see which direction the merge should be. For merges that have different LNAB's there is a option on both options to reverse the merge. See
and
Both ways show an option to reverse the merge because sometimes people do set up merges into the wrong name. For different LNAB options there is not a requirement to do the merge into the lower numbered profile but some people obviously do this. For your example profile it looks like you set up the merge into the correct LNAB but someone reversed it into a lower numbered LNAB instead. So it is human error and not a computer error.
Michel, The comment on https://www.wikitree.com/wiki/Bremer-160 shows that the merge was supposed to go into the Andries-550 profile. The message on https://www.wikitree.com/wiki/McAdoo-133 which is what I used as my example screenshots shows the merge was supposed to go into the McAdoo-133 profile.
That means that you did set up the merge in the correct direction. So The "First Option" shown on the pending merges screen should have been merging incorrect LNAB into correct LNAB. That is taking the proper direction into account. The only ways to get it going the other way is if someone clicked reverse merge or they did the merge from what should have been the destination profile and ignored the profile comment and the warning message to check what the LNAB should be. So it could be considered a human error assuming the person made a mistake.
