this is not a new problem, we had that before, though it was hidden. and even more weird, as we took the backend path and if there was a move, applied that again before requesting the node. i suggest we keep that known bug for the moment, until somebody wants to implement that method to walk the move operations in the other direction.