I have this problem specifically with “Return Node”; if the error happens at some point during a cast, interface message, or function, or macro, or whatever, the system seems to grab the first “Return Node” it finds and report THAT as the problem, rather than whatever node is actually DOING the returning.
I assume that’s just a quirk of UE4, something to do with the generic-ness of return nodes in general.