Runs, batches & results
Full workflow run
Run all evaluates the complete directed graph. Dependencies are resolved lazily, so a node waits for its upstream values even when several independent branches are running at the same time. The server runs up to four independent graph evaluations concurrently.
Canvas-only Sticky Note and Group nodes are marked skipped and never sent to a handler.
Run one node
The Run button on a node starts a partial rerun for that node and its downstream consumers. Upstream results may be reused only from a server-owned project version; the browser cannot supply an arbitrary result cache. Reused nodes are reported as skipped.
Editing a node clears its own result and cached downstream results in the current tab so an old image or text is not presented as fresh output.
Statuses
| Status | Meaning |
|---|---|
idle | The node has not participated in the current run. |
running | The handler is executing or waiting for a provider. |
done | The node completed and produced its declared result. |
blocked | A required input is absent, has the wrong kind, or an upstream node produced no usable value. |
skipped | A canvas-only node or an upstream result reused during partial rerun. |
error | The handler or external provider failed. Other independent branches continue. |
An empty output from a node that declares an output is treated as blocked, not as a successful empty result.
Batches and fan-out
Text variables, iterators and multi-result nodes produce streams. When a node consumes several streams, combinations are calculated as a Cartesian product.
Example: 3 hooks × 2 images × 2 CTAs produces 12 variants.
The default maximum is 100 combinations per node. An administrator can configure the value between 1 and 1000. When the limit is reached, the node logs a truncation warning and processes only the allowed prefix.
Results
- Text results can be copied individually or as one combined block.
- Media results support carousel and gallery views, sorting, full-screen preview and download.
- A multi-result media node can be unpacked into individual Import nodes.
- Image results can be converted into an Image Iterator.
- Export all downloads the current media batch as a ZIP.
- Large server results are explicitly marked as truncated. Load more results requests subsequent pages of 100 after the run finishes.
Generated assets also appear in Library when the corresponding handler records a generation. Pure passthrough, selection and local helper results are not necessarily added to Library.
Stop and tab ownership
Stop cancels the active server run. Each request is bound to the tab and project that started it through a client request id, so late SignalR events are routed back to their owning tab instead of whichever tab is currently open.
Logging out attempts to stop active runs, disconnects SignalR and clears tab/run ownership state.
Errors and history
Node errors include the message on the node. The server stores bounded node parameters and resolved input references for diagnostics; raw media bytes are not placed in the error context.
A successful project run can create a project-history checkpoint containing the graph and typed result references. Failed or blocked runs are reported with their counts and do not masquerade as a fully successful run.