Flow Editor glossary

Use this as a quick lookup while reading a guide. Node and port names such as Condition, Match and Order Ticket remain in English across both locales. The linked articles explain the full behavior behind these short definitions.

A–C

Activation — One occasion on which a strategy evaluates an executable path. A primary trigger starts it; a wait can resume the same path.

Alert — A node that records a message when its control path reaches it. A Backtest simulates the Alert; saving a strategy does not send email.

Backtest — A simulation of a saved strategy over a chosen historical window, data and cost assumptions. See run a Backtest.

Bar — Market data summarized over one interval, commonly with open, high, low, close and volume. A one-minute bar does not guarantee an action every minute.

Canvas — The visual area that contains nodes and connections. Position alone does not decide execution order.

Checkpoint — A named historical point created for recovery or comparison.

Condition — A decision node that compares values when control reaches it. Match and No Match are control outcomes; Result is a Boolean data output.

Control connection — A connection that determines what can run next. It does not carry a market value.

D–P

Data connection — A connection that provides a typed value to an input. By itself, it does not start an action.

Data Port — A typed input or output exposed by a node. Some ports appear only for a selected operator, source, role or mode.

Dirty — A state indicating local changes not yet confirmed as saved. A pending save, offline state or conflict needs recovery.

Edge — A connection between compatible handles. Check whether it carries control or data.

Inspector — The panel for selection details, Parameters, Outcomes, and Data Ports. Active fields depend on the configuration.

Literal — A value entered in a node setting, such as Condition's right-hand threshold of 60. It replaces a data-port input only where that configuration supports it.

Node — A graph element with a defined role. It can provide data, receive control, branch, wait, act or annotate; see node anatomy.

Outcome — A possible control branch of a node, such as Match or Submitted. A data output is not an outcome.

Parameter — A saved setting that configures a node. A field may be required only for the selected variant.

Primary activation — The single general entry point required by a valid graph: Event Trigger in Tactical or Schedule Trigger in Portfolio.

Q–V

QHM Metric Value — A data node for an eligible Quant Hub metric version. Visibility in the research catalog alone does not guarantee Flow eligibility.

Quick add — A menu of nodes compatible with a selected connection handle.

Replay — Read-only inspection of debug data recorded by an eligible Backtest. Availability depends on the run's debug setting and retained data.

Restore — A non-destructive action that creates a new current version from historical content.

Risk limit — A configured bound such as maximum asset weight or leverage. Its unit, role and applicable data determine what is checked.

Tactical — A strategy mode for supported market-event and instrument logic. Event Trigger is its primary activation.

Portfolio — A strategy mode for scheduled asset allocation; an auxiliary safety path is limited to supported protective actions.

Timeframe — The interval used to group market data; 1m means one minute. It does not promise a signal in every interval.

Validation — Checks that report graph problems and readiness. Passing graph validation alone does not guarantee enough market data for a run.

Variable — A declared named value that Read Variable can expose and Set Variable can update.

Market data and results

Bar — Market data summarized over an interval, including open, high, low and close prices. Timeframe defines that interval; 1m means one minute.

Warm-up — Earlier observations needed to initialize an indicator before the tested period can be evaluated. Missing history is not numeric zero.

Greater than — A comparison that is true whenever the left value exceeds the right. Crossing above additionally needs a previous value on the other side; the two conditions are different.

Order Ticket — The reference returned after accepted order submission. Order Result describes an observed later lifecycle outcome. Submitted does not mean Filled.

Target weight — A desired share of an allocation, such as 0.5 for 50%. The Inspector can display a percentage while the graph stores a fractional value.

Equity — Account value including open-position effects when supplied by the result. Drawdown measures decline from a previous peak.

Retention — How long particular stored data remains available. A saved bookmark does not extend detailed Backtest or replay retention.

Overlay — A visual layer on a chart. Quant Hub overlays do not become strategy inputs or alter a Backtest.