FL Node Pack Loader

This is a niche one, and if you're a beginner the honest advice is you probably don't need it - but it's small and worth understanding, because when you do need it, nothing else quite does the job. FL_NodePackLoader is a pass-through node whose only trick is that it always reports itself as "changed," which forces the node it feeds to re-execute every time you run the graph, even when ComfyUI's caching would otherwise skip it.

How it works

ComfyUI is aggressive about caching. If a node's inputs haven't changed since the last run, it reuses the cached result instead of recomputing - which is great for speed and occasionally maddening when you want something to re-run. Nodes signal whether they've changed via an IS_CHANGED value. FL_NodePackLoader sets its IS_CHANGED to NaN, and because NaN never equals itself, ComfyUI always sees it as different and never caches it. It passes a TRIGGER straight through, so whatever depends on that trigger gets pulled fresh every execution.

In plain terms: it's a "re-run this branch, no matter what" switch, dressed up as a loader. It pairs with the pack's FL_NodeLoader (a plain trigger pass-through) in dependency-management setups where you're using triggers to order execution.

The inputs and output

• trigger - a TRIGGER input. This is a control-flow signal, not image or latent data.

Output is a TRIGGER, passed through, but now carrying the always-changed behavior so anything downstream of it re-executes.

Installing it

Comes with the Fill-Nodes pack. ComfyUI Manager: search ComfyUI_Fill-Nodes, install, restart. Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/filliptm/ComfyUI_Fill-Nodes

then restart. The "Machine Delusions" splash banner on startup is cosmetic.

Where people get tripped up

• This is advanced control-flow, not a content node. If you're building normal image/video workflows, you almost certainly don't touch this. It exists for people orchestrating execution order with trigger wires - a small audience with a real need.
• TRIGGER isn't a data type you can plug anything into. It only connects to nodes that emit or accept triggers (like FL_NodeLoader). Don't expect to wire a model or image into it.
• Forcing re-execution has a cost. The whole point is defeating the cache, which means the downstream branch recomputes every single run. That's exactly what you asked for - just don't be surprised when a graph with this in it stops being snappy on repeat runs.
• If you're here because a node won't re-run when you want it to, this is the fix. If you're here because you clicked something at random, it's safe to ignore.