There appears to be a bug in the way we pull target entities on initial import in situations where the target entity is determined multiple times on a single request... The bug is resolved by re-evaluating translation sets before pulling the target node, but I haven't yet found the circumstances for the bug / a solid repro...
There appears to be a bug in the way we pull target entities on initial import in situations where the target entity is determined multiple times on a single request... The bug is resolved by re-evaluating translation sets before pulling the target node, but I haven't yet found the circumstances for the bug / a solid repro...