I’ve also recently had this issue. I have multiple columns with links and needed to solve it by having extra seatable nodes querying the ressources and merging them back together.
It was quite a painful and long process for something that I expected to be done by that option, actually.
Right now I don’t have a system to reproduce this at hand, but it sounds to me now with two confirmations that it should be reported upstream in the N8N issue tracker:
IIRC from SeaTable API use, the link / table relation can flip depending in which table the link was created. Perhaps it’s just an off-by-one error looking up the ID in the wrong table and then getting empty results, but as written, I can not reproduce this right now, sorry.