Condition

Compares values and selects Match or No Match.

When to use

Use Condition when the control path must branch according to a value comparison. It needs a control arrival from an executable path and the values required by its chosen operator. A data edge into Left alone does not start the decision. Condition works in Tactical and Portfolio; some operators, including crossAbove and crossBelow, have their own Pro requirement.

Example

In an RSI alert, connect Event Trigger.On Event → Condition for control and Indicator.RSI → Condition.Left for data. Set Operator to >, Right source to Literal, and Right literal to 60. Connect Condition.Match → Alert. The literal supplies the right-hand number inside the node, so no Right data edge is needed. In the Inspector, the Right handle is inactive for this choice.

This is a level comparison: consecutive bars above 60 can reach Match repeatedly. An operator that tests a crossing is a different choice and can require previous values and a different plan. The table is a teaching example with supplied RSI values, not a measured historical run.

To compare two changing values instead, choose Right source = Data Port and connect a compatible value to Right. The active fields and ports then change. For equality or inequality, select the literal's type where requested; for unary isTrue or isFalse, there is no right-hand comparison value. Read the generated conditions below as possible configurations, not fields to fill simultaneously.

Try it here

Explore Condition

Compares values and selects Match or No Match.

Exercise steps

1. Change Right source from Literal to Data port.
2. Observe the required Right input and its validation; return to Literal to fix it.

Start lesson

Common problems

If Right is missing, first check whether you selected Literal or a unary operator; that can be correct. If you cannot connect Bars to Left, use a compatible scalar such as Indicator.RSI rather than a bar collection. If the node looks configured but Alert never runs, trace the control path from the primary event to Condition, inspect the active Left input, and check which outcome is connected. Result is a Boolean data output; it does not replace the Match control edge. An unused No Match branch may be intentional and can be informational rather than blocking.

Validate the whole graph, then save and reopen it before treating the configuration as persistent. A graph with Condition and Alert but no Order does not create trades. For a complete five-node walkthrough, use the RSI Momentum Alert.

Next steps

Use the generated Parameters, Outcomes, and Data Ports below to check the option and port active in your configuration. Continue with nodes, ports, and outcomes if the distinction between Match and Result is unclear, or connection troubleshooting if an edge is rejected.