Skip to main content
In the editor, supported server-side nodes can run by themselves without running the whole graph. It’s the fastest way to test a model or server operation before committing to a full run. When you run a single node, Blend AI resolves just that node’s inputs from whatever is wired upstream (or already produced), runs it, and streams the result back live.

​
Supported nodes and modes

The Run action is allowed only when the node’s current mode executes on the server and explicitly supports standalone execution. Required model, parameter, and upstream input validation still applies.

​
Where the result lives

The result lands on the node itself. Each node keeps its own append-only history of its single-node runs, so every time you run it again, the new output is added — it doesn’t overwrite the last one. Flip back through previous outputs right there on the node to compare what changed as you tweak settings.

​
It is not a workflow run

A single-node run is for iterating, not shipping. It does not create a workflow run record.
Nothing from a single-node run appears in history. If you need a run you can find later, share, or reference, do a full run instead.
Iterate on a node with single runs until it’s right, then do a full run to capture the finished output.

Running the full workflow

Run the whole graph end to end and produce a run you can keep.

Results & history

Where full runs are recorded, and how to find past outputs.