SET and GET node incorrectly detect input/output undefined.

[Trung0246]

SET and GET node is heavily dependent on node load order, hence will throw alert if output is undefined, despite being the node connected to is valid and will load later then SET and GET.

ComfyUI-KJNodes/web/js/setgetnodes.js

Line 104 in 1ec5810

if (link_info && node.graph && slotType == 1 && isChangeConnect) {

I've suggest to wrap entire check around setTimeout or maybe update SET/GET node after all nodes are loaded.

[kijai]

Can you give an example where this would happen? Never experienced this kind of issue myself, is this about compatibility with other custom nodes?

[Shyryp]

I think I started getting this problem too.
Moreover, it is completely incomprehensible to me and appears when I load a workflow from a json file.

Screenshot of the error:

I use Easy-Use cycles, could there be a problem with them?

Here is a screenshot of the cycle and the Set nodes used near them:

The error I get, it is not clear which node it points to. But I assume that this is precisely because of the use of Easy Use in cycles. Perhaps it is the "Start_Index" node in my case, since after deleting it, the error stopped appearing after reopening the workflow.

[Shyryp]

The problem can especially arise if Set was accidentally reconnected to a certain variable type (for example, INT), and then reconnected to an unknown *. In this case, Set continues to consider the input as INT, although on the Set node itself it is specified as *.

Example (look at the color of the line, it has become dark blue, which means INT - this leads to an error when opening a workflow in Comfyui):

Of course, in this case, the Get nodes stop being defined as IMAGE and break the connection, and therefore it is not a problem to figure out the problem in this case.

HOWEVER! This problem can also randomly appear even if I do not change the Set and Get nodes in any way! That is, the problem can suddenly appear from unknown actions.