Flow Editor guides

Choose the result you need and keep the guide open while you work. A guide describes an editor task; use concepts for the reason behind a rule and the node reference when a field or port depends on a particular node.

Build and edit

For a new graph, work through these tasks in order:

1. Create a strategy to choose the mode and a blank graph or available Starter.
2. Add, move, duplicate and remove nodes. Quick add helps when you start from a connection handle.
3. Use the Inspector and configure a node. Active controls can change with the selected operator, event or role.
4. Connect nodes to complete control and data paths. A data edge alone does not start an action.

For a first complete build, the RSI quickstart makes this sequence concrete. When modifying an existing graph, identify its mode and current saved version first.

Prepare and protect

• Fix validation issues to distinguish a missing required input from an informational unused branch. Validation checks graph readiness, not the quality of a trading idea.
• Manage variables when a value must be read or updated within the Flow's defined state scope.
• Configure Settings and visual preferences to distinguish strategy settings from local viewing choices.
• Save and resolve conflicts before leaving. A pending save, offline state or conflict is not a confirmed version.
• Create checkpoints and restore versions before an experiment or to recover historical content. Reset a flow explains its separate backup, confirmation and recovery path.

Test and navigate

Add a Quant Hub metric only after checking eligibility for the current mode and plan. Run a Backtest from a saved, ready graph; use Backtest Center to inspect its state and results. Debug and replay applies to runs that recorded the required debug data.

Use keyboard shortcuts and the tablet and mobile guide if your input method or screen size changes. The same validation and save checks still apply.

Choose by symptom

If a port is absent or an edge is refused, start with connections and data types. If the graph appears connected but no action occurs, check activation and validation. If work disappears or cannot save, use save, offline and conflict recovery. The troubleshooting index groups the remaining cases.