Why does a node re-execute a previous node when there already is output data?

As I am working on my workflow, one issue that keeps making it difficult, is that a previous node is re-executed for no reason it seems, and this could be a node that sends http requests that costs us money and time. I can understand previous nodes might need to be re-executed if there is dependent data, but I have seen this happen even when the node has all the data it needs. Why is it done like this?!

1 Like

Hey @King1 hope all is good. Welcome to the community.

Does pinning the information in the node help?

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.