The problem isn’t the node, it is how Dynamo functions. Assuming you have saved the graph at some point during the run, the problem is called Element Binding (as @Mark.Ackerley mentioned). Check out this post for more detailed information on what is happening: Element Binding in Revit by @jacob.small
A quick solution is to use Dynamo player as that avoids element binding. Another solution is to clear the bindings, save the graph, and then when you use the graph again, do not save it afterwards. Close the graph, reopen, and run again. Just make sure you do not save between runs as that will create element bindings.
Easy way to clear the bindings is to disconnect all the inputs so that when you run the graph, wherever elements are supposed to be seen should be replaced with nulls and the graph should be filled with errors. The other way is to open the graph in a .txt editor and manually clear them.