If you merge entity A with entity B, and B is being merged with entity C, but B -> C happens first, then A -> B fails. If the outcome of merging is that the merge target takes on the identity and relationships of the merge subject, I don’t understand why the system can’t handle this. It seems like simple logic, A=B and B=C therefore A=C.
Is there a ticket for this by any chance? It’s quite a nuisance trying to keep track of C so I make sure that A and D and E all get merged with it instead of B.