-
Occasionally, especially when dealing with nodes that save things or show a string or whatever, I can mute or bypass everything UP TO the final node. But because the bypasser takes OUTPUTS, rather than (or additionally) having a node that executes the bypass forward, there's often a node that is last in the chain that can't be bypassed: The WF still runs, but throws errors in console and redboxes the node, which is confusing to users. How might I mute the last node in this (or really any) chain? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Unfortunately, for the original Fast Muter/Bypasser the node must have an output to connect it to. In your example it's actually OK that the Image Save node isn't muted because you've muted the nodes that connect into it. Like in your screenshot, it will turn red because it thinks there's an error, but as long as you have another output node (Image Preview, Image Save, etc) it won't actually stop the execution; just be red which is fine. If you want to mute everything, including nodes w/o outputs, you can put them in a Group and use the Fast Groups Muter or Fast Groups Bypasser, which will have toggles for each Group and mute/bypass/enable everything in the group at once. |
Beta Was this translation helpful? Give feedback.
Unfortunately, for the original Fast Muter/Bypasser the node must have an output to connect it to. In your example it's actually OK that the Image Save node isn't muted because you've muted the nodes that connect into it.
Like in your screenshot, it will turn red because it thinks there's an error, but as long as you have another output node (Image Preview, Image Save, etc) it won't actually stop the execution; just be red which is fine.
If you want to mute everything, including nodes w/o outputs, you can put them in a Group and use the Fast Groups Muter or Fast Groups Bypasser, which will have toggles for each Group and mute/bypass/enable everything in the group at once.