search

ltdrdata / ComfyUI-Workflow-Component

This is a side project to experiment with using workflows as components.
GNU General Public License v3.0
214 stars 9 forks source link

Node types were not found... #16

Closed hightechpresha closed 1 year ago

hightechpresha commented 1 year ago

Hey ltdrdata,

I watched your video tutorial on the topic: "ComfyUI Workflow Component - Component Creation Tutorial". I exported the newly created component using the Export As Component button. When I drag and drop the component into an existing workflow it is also displayed correctly. If I now save the workflow, close Comfyui and start it again, I always get the following error:

node types-not-found

Error: When loading the graph, the following node types were not found: "## AIO-Advance-KSampler [b8a908]" Nodes that have failed to load will show as red on the graph.

Where is the error in my walkthrough and how can I fix it?

ltdrdata commented 1 year ago

Hey ltdrdata,

I watched your video tutorial on the topic: "ComfyUI Workflow Component - Component Creation Tutorial". I exported the newly created component using the Export As Component button. When I drag and drop the component into an existing workflow it is also displayed correctly. If I now save the workflow, close Comfyui and start it again, I always get the following error:

node types-not-found

Error: When loading the graph, the following node types were not found: "## AIO-Advance-KSampler [b8a908]" Nodes that have failed to load will show as red on the graph.

Where is the error in my walkthrough and how can I fix it?

Did you save the workflow as "Save Full" when saving? The difference between "Save" and "Save Full" is whether the components are stored within the workflow itself or not. To load a workflow saved with just "Save," you would need to externally read the components, so the corresponding component file should be located in ComfyUI-Workflow-Component/components.

hightechpresha commented 1 year ago

Thanks ltdrdata,

that was exactly the problem. After saving the workflow via the Save Full button the error did not get anymore.