DAG Nodes
Workflows in the HQ visual editor are built from typed nodes connected by edges. Each node has its own execution semantics and configuration surface.
Available node types
Section titled “Available node types”| Type | Purpose |
|---|---|
| Start | Entry sentinel. Receives the trigger payload. |
| End | Exit sentinel. Marks where a graph run finishes. |
| Skill | Executes a skill (LLM task) on a minion. |
| Review | Human or minion approval gate with revision loop. |
| Fan-out | Expands a sub-graph over an input array. |
| Join | N-input barrier that aggregates upstream outputs. |
| Conditional | Routes execution down one branch based on a condition. |
| Transform | LLM-driven contract bridge between two edge contracts. |
| Script | Run an inline Python or Node.js script — deterministic, no LLM. |
How nodes fit together
Section titled “How nodes fit together”flowchart LR S(("Start")) --> A["Skill: fetch"] A --> C{{"Conditional"}} C -->|ok| T["Transform"] C -->|error| E(("End")) T --> F[["Fan-out"]] F --> J(("Join")) J --> R{"Review"} R -->|approved| E R -. revision .-> AStart and End are sentinels — the editor inserts them automatically and they do not appear in the node palette. Every other node type is drag-and-drop from the palette on the left of the editor.
Common fields
Section titled “Common fields”Every node has these fields in the property panel (rendered by the common header, not by the type-specific section):
| Field | Description |
|---|---|
id | Stable identifier, unique within the graph (and within each template). |
label | Human-readable display name on the canvas. |
Every step runs on any minion that is a member of the project. To have a particular minion run a step, pin it under Who runs each step on the workflow’s page in the project (the pin only applies to that project). Workflows made before project roles were retired may still name a role (assigned_role) on a step; it is ignored, and it is removed when the workflow is saved or published.
For type-specific configuration, see each node’s page.
When a step fails
Section titled “When a step fails”A failed step shows why it failed on the run’s page:
| Shown as | What happened |
|---|---|
| Timed out | The step ran longer than its time limit. |
| LLM authentication failed | The minion’s LLM CLI is not signed in, or its key was rejected. Someone has to sign it in again. |
| LLM unavailable | The LLM was busy, hit a rate or usage limit, or ran out of credit. |
| Run error | The LLM CLI exited with an error. |
| No output | The step ended without handing in an output. |
| Contract violation | The output did not match the edge’s Contract. |
| Declared not completable | The step itself reported that the task could not be done. |
| Failed to start | The step’s session could not be started. |
| Script failed | A Script node exited with an error, printed something that is not JSON, or timed out. |
| Minion stopped responding | The minion running the step went silent for 5 minutes. The run moves on instead of waiting forever. |
| Marked as failed manually | Someone pressed Mark as Failed. |
| Execution stopped | Someone stopped the run. |
Retrying failed steps automatically
Section titled “Retrying failed steps automatically”Turn on Retry failed steps automatically in the editor’s Settings tab to have a workflow retry steps that failed for a reason another attempt can fix. Choose the maximum number of attempts, from 2 to 5, counting the first run. Retries are off by default, because every retry uses the LLM again.
- Retried: minion stopped responding, timed out, LLM unavailable, run error, failed to start, no output, Contract violation.
- Not retried: LLM authentication failed (it fails the same way until someone signs in), declared not completable, script failed, marked as failed manually, execution stopped.
- The next attempt starts 1 minute after the first failure, then 5 minutes after each later one. The step is told why its previous attempt failed.
- A retried step shows Attempt 2/3 on the run’s page, and its earlier attempts are listed under it.
- For a step that must not run twice, such as sending mail, tick Never retry this step in its properties.
- The setting is saved with the workflow, so it applies to runs started after you publish.
Sharing outside the workspace
Section titled “Sharing outside the workspace”You can publish a workflow’s design so people outside your workspace can see it. The editor’s Publish button is a different thing: it fixes the version your workspace runs, and shows nothing to the outside. For publishing outside, see Public sharing, and What gets published for what people can see.