interface/features/subgraph

[giscus[bot]]

interface/features/subgraph

An introduction to the Subgraph feature in ComfyUI, including how to create, navigate, and manage subgraphs.

https://docs.comfy.org/interface/features/subgraph?utm_source=substack&utm_medium=email

[kuchinal]

Hi folks, looks great, works good so far, very intuitive design.
Few points so far:

• missing ability to reorder inputs
• will be great to add an ability to create tool tips for exposed inputs (if we do create a black box to protect the user from the complexity of comfy - will be great to give some info of what every knob does)

Thank you very much!

[hoaxgames]

I would like to know if there is a way to reuse / search for the generated subgraphs in different / the same workflows?

[comfyui-wiki]

That will be supported. The current version is the first subgraph version, and we have other subgraph features still in development.

[PopHorn]

How to convert a subgraph back to initial nodes?

[comfyui-wiki]

This feature is still under development. It will be supported soon. Check here: Comfy-Org/ComfyUI_frontend#4840

[JohnneyTexas]

You're incorporating a defective product that doesn't even implement basic functions into the standard features, and then forcing that defective product to be applied with every update. That's quite INSANE.
Do you really think you've worked hard after just a few months of work?

DON'T BE SPOILED!

[voradori]

as what I see this is NOT like UEs collapse to function/macro etc

Just do this

1. Make subnode

2. Copypaste it to somewhere

Result:

They are same but technically different nodes
Not different "instances" of same node
If you edit something inside one node, nothing is changed in second

So you need to manually replace all the nodes with a new one

As I'm used with UE nodes/blueprints system - I expect that if you change code inside, inputs etc, it changes everywhere it is used, immediately, without breaking pins or inner spaghetty

And what I see is nothing like this

I did not found any way subgraph can behave like UE nodes

[comfyui-wiki]

Don't worry, the linked subgraph instance is also part of the development plan. The current version isn't the final one. There are still some features under development.

[ascendingauthor-prog]

I couldn't find a way to expand a subgraph back into its parent, i.e. to undo the effects of the four-inward pointing arrows icon "covert selection to subgraph".

Obviously ctrl-z will do that immediately, I'm thinking of wanting to re-expand the subgraph days later. Say if one of its nodes has been upgraded or I want to use a better node from a different custom node pack, but the new node's process flow requires some rework. Maybe the old subgraph needs to be re-expanded, enhanced, and then turned into two subgraphs on either side of some parent-level nodes.

[comfyui-wiki]

All the features you mentioned are already under development. Currently, the subgraph still needs several iterations to complete the final features.

Comfy-Org/ComfyUI_frontend#4840

[ascendingauthor-prog]

Thanks for the quick reply. I'm looking fwd to subgraphs. I'm the sort of guy who finds untidy spaghetti strands annoying, but I don't know ComfyUI well enough yet to turn them off.

PS. I noticed another tiny issue that I'm 99.9% sure has been spotted already, but just in case:
During a Run cycle, nodes are outlined in green to indicate which node is processing. When a SubG is reached, the previous node stays greened. (Don't bother replying to this.)

[JohnneyTexas]

While the concept itself is brilliant, the actual product is poorly tested and lacks sufficient functionality. Your W/F will not function properly in the version with this feature implemented. Even if it worked properly, the D/D in the image would be unusable. Frankly, there's no benefit to this other than satisfying the ego-show-off desires of low-level engineers.
In other words, the content presented here is just fantasy.
Any decent engineer would first put all their efforts into fixing the reported bugs. They wouldn't even have the time to mindlessly reply to comments.

comfyanonymous/ComfyUI#9217

[ascendingauthor-prog]

I, for one, want to lodge my disagreement with the tone of the above comment. I am happy to have subgraphs coming, and aren't upset by the process being gradual. I can choose to use what already works, or not use it at all. I'm perfectly fine with learning about it now so I'll be ready to use it fully when it's powerful enough.
Keep up the good work, guys.

[JohnneyTexas]

Yes, if you have only simple workflow that you to innocently rejoice and say "Wow, I managed to generate it!", you would not to face with many troubles to identify the reason why it doesn't work by your self, come up with a solution to the bug where even if you make a correction and save it, the changes aren't reflected (although this may have been resolved now), sometimes have to manually edit JSON files and navigate through complex node configurations to make the appropriate corrections b y yourself on all in multiple workflows.

[set-soft]

I really like subgraphs (in fact I was one of the users that asked for it)
And is fine for me that they are deployed gradually. I.e. inputs needs to allow editing its order, mechanism to reuse them are needed, etc.
What I don't understand is why "grouped nodes" is no longer supported. Why aren't they imported as subgraphs?
And I think @JohnneyTexas is upset about it (look at the issue linked by the user).
I don't agree with the strong language and wrong attitude, but then again, I can't believe that when you open a workflow with grouped nodes you get a broken workflow, all groups broken.

[evanerichards]

It would be great if you could add separators or custom colors to sections of the sub-graph node. I have a node now that encompasses my enitre workflow but all of the sections are together in one big long node. Would be great to add a seperator between the k-sampler settings and the upscaler settings for instance.

Thanks for building this! This is awesome.

[Pam-Devil]

I wantto know if there is currently a way to save a subgraph to be reutilized in other workflows? The way we did with group nodes. Because currently i cant find anything on the internet about saving subgraphs and searching for them. If not, i hope this feature come soon, because it's one of the core reasons why i used group nodes in the first place.

[comfyui-wiki]

Both this feature and the linked subgraph instance are in the development plan. They just need some time to implement. :)

[farting-backwards]

Subgraphs have the potential to be a powerful feature in ComfyUI. However, today they are buggy and incomplete. I wonder how the decision was made to release this as a production feature. It was not the right decision.

In six months, maybe we'll have a mature, useful subgraph system. Today, previously-working graphs are broken and the intended replacement for the broken features is also broken. It's a deeply unfortunate situation and I hope the ComfyUI team fully understands just how badly they've damaged their product in the short term.

[comfyui-wiki]

Can you provide more details? Any workflow or logs?

[farting-backwards]

Sorry, I wrote that post in my crabby voice. I had just lost work. The sentiment still stands (there is potential, but it's not currently realized), but I'd say it nicer if I was writing it now.

• In an empty canvas, place a Split Images node from comfyui-videohelpersuite.
• Right click on it->Convert to Subgraph
• Open the new subgraph
• Drag the input node to the split_index widget, or vice-versa
• Exit the subgraph and the UI goes unrecoverably haywire. Reloading the page doesn't work. If you saved the workflow after connecting the input node, loading the graph crashes the interface again. Whatever work was in that graph is lost as far as I can tell.

I've encountered one other data loss bug while working in a subgraph, but I don't know how to reproduce it. The manifestation was that the parent graph ceased to exist. Breadcrumbs vanished and I was trapped in my subgraph, unable to access the rest of my workflow.

And editorially, until subgraphs are instatiations of a base object, they're only a fancy way to copy/paste code. I don't want to have to edit all of the subgraph copies in my workflow; I want to edit the template/class/base workflow and have that affect all the instances.

[TheArtOfficial]

It would be awesome to see animated previews on the subgraph if a sampler is running inside of it! Thanks so much for the work you do, love the initial subgraphs, can't wait to see where it goes.

[TheArtOfficial]

Along with this, I'm really looking forward to subgraphs being searchable.

[comfyui-wiki]

My colleagues are still working hard on these new features. Some of them are already supported now, but they haven’t been fully merged yet.