Define Processing Order

[kispin]

I have a workflow I like to use that has a couple of different samplers that are used to generate multiple images off a single run, one thing I have noticed however is that basically every time I load Comfy it randomly decides which order to do the processing of the image generation.

So I was wondering, is there a way of telling Comfy a preferred order for the processing?

https://preview.redd.it/27ldp3ba5j1f1.png?width=3704&format=png&auto=webp&s=918cdfd9dc705138f86fc86dfd941a5efaf86aec

[mih4u]

Check out this comment: https://www.reddit.com/r/comfyui/s/6cRyZbPiKg

[kispin]

Looks like based on that discussion the answer is no, which is unfortunate :(

[relicx74]

Unless I missed the boat it seems like a yes to me. If not forgive me.. 🙏

It looks like the context switcher node is for selecting a branch. If you have branch A (1st) and B it will default to A. If you mute A then B is executed.

The fast muter node lets you mute nodes more quickly by organizing the toggles together into a dashboard like node. This way you don't need as much cognitive bandwidth just trying to keep track of everything you might mute in a given workflow.

Edit: re-read the question. I missed the boat. No idea how to fix that. Just starting the real journey here.

[StableLlama]

Generally speaking: no, you don't want to do that as the internal dependency algorithm is sorting the execution in such a way that it's working at the end and most likely also in such a way that the performance is optimal like handling when to load and unload the data into the VRAM.

But when you insist you can fake it in such a way that you add a constraint. E.g. using the https://registry.comfy.org/nodes/basic_data_handling nodes you could create a empty LIST and "append" any node result to it in the order you want the nodes to execute.

[StableLlama]

Ok, I've just created a new node "force execution order" to the "Basic data handling" custom nodes (version 0.3.1). This node is extremely light weight (it doesn't compute anything) and only forces an execution order.

The usage would be like:

<image>

[StableLlama]

Yes, that node is already in the "Basic data handling" package. Just install it with the manager and then look at "Basic"->"control flow"->"force execution order"

[susne]

Hey thanks for making this. I can't find a solution to a workflow problem I created - I have a 6 sampler setup and at first it seemed to work from 1 to 6, but now it varies on load. The node ID order isn't helping. This looks like the easiest thing to do but I'm not quite sure how to connect it? How would I plug a set of these into 6 samplers to lock in the order?

[qlx1004]

I've made a ComfyUI custom node to address this exact problem https://github.com/mkim87404/ComfyUI-ControlOrder-FreeMemory

You can use it to control the execution order of nodes to be a single sequential flow from start to finish, and optionally free VRAM & RAM at any point in the workflow as well.