Fear, anger and joy, this is the typical three emotional stages when working with a ComfyUI workflow.

In RunComfy we support tens of thousands of ComfyUI users which makes us handyman of your ComfyUI environment.

“To cure sometimes, to relieve often, to comfort always”.

Fear and joy is not within the scope of this how-to, but we can provide a framework to alleviate the anger.

Mental Meditation

  1. It is not my fault,
  2. There is a fix to anything broken, just a matter of time and money.

Nodes Complexities

Missing Nodes

  1. Thanks to ComfyUI Manager, you just need to install missing nodes from there.
  2. Pay special attention to channels, certain nodes only exist on certain channels.
  3. Search in https://registry.comfy.org/ if the install doesn’t work and follow the instruction there
  4. Sometimes the name in error message only exists in code, please try searching them here as well.

Conflicting Nodes

  1. Versions
    1. You will eventually encounter two nodes ask for the same lib but conflicting versions
    2. Node A asks for huggingface-cli > 0.26, Node B asks for huggingface-cli < 0.26
    3. This is not your fault and not a bug of ComfyUI, not a bug of the nodes, not a bug of RunComfy, but an inherent byproduct of an open extension system.
    4. You can try the following
      1. File a bug in the node github repo and tell the node author to specify the lib version explicitly as a good Python samaritan should.
      2. But that doesn’t really fix the conflicting versioning issue, since most authors just lock the packages with the latest version which still conflict with other nodes. You can find the requirements.txt in the node A, normally it is easier to downgrade the package version since the new version might have incompatible changes. Change the huggingface-cli > 0.26 in the requirements.txt to a lower version. If the requirements.txt doesn’t contain the offending package huggingface-cli, that means some package X in this requirements.txt is referring to huggingface-cli that you need to fix that package X to a lower version, in our case it is transformer package that we need to lower the version.
  2. Names
    1. It is rare that two men have the same taste and same drive and same naming strategy when it comes to node names, but sometimes you will find “GetNode” or “SetInt” or some total random node name that is not working correctly. Please do check if you are referencing the wrong node with the same name, it happens.

Obsolete Nodes

  1. Nodes authors will write nodes that does exactly the same thing, or just run the same model with different node names. Please do make sure you try both nodes with similar names and pick the one that you are comfortable with. Check the following signals,
    1. Last commit date, the later the better
    2. Responsiveness in Github repo bugs and commits
    3. Reputation, when you see Kijai/Matteo node and anyone from Comfy team, please use theirs.