Blocker

The Blocker node is a conditional data-flow gate in the EasyUse/Logic category. It passes the value received at its in input through to its output only while the continue toggle is True. When continue is False, the data flow is blocked, making this node useful as a manual switch, safety gate, or branch disabler inside a workflow.

Inputs

continue

• Type: BOOLEAN
• Required: Yes
• Default: false

Boolean control for the gate. Set this to true to allow the in value to pass through to the output. Because the default is false, a newly added Blocker will stay in its blocked state until you explicitly enable it.

in

• Type: ANYTYPE
• Required: Yes

The value that should pass through when continue is true. Since this input accepts ANYTYPE, it can be connected to almost any node output — models, latents, images, conditioning, prompts, or arbitrary data.

Outputs

The node has one output of type ANYTYPE.

The output mirrors the value from in when continue is true. When continue is false, the output is effectively blocked, so the node should not be relied on to provide a usable value to downstream nodes.

Usage Notes

• The default state is blocked, so inserting a Blocker into an active workflow will immediately disable downstream data flow unless continue is set to true.
• This node does not transform the data passing through it; it only gates whether that data is forwarded.
• Because in and the output are both ANYTYPE, the Blocker can be inserted into a wide variety of connections without changing the underlying data type.
• It is especially useful for temporarily isolating a branch, comparing conditional paths, or keeping a workflow “stalled” until a particular condition is manually or programmatically set.