Help center
Connections Between Blocks
by QATS • Feb 7, 2026
Connections and configuration
Connections define how your strategy flows from one block to another. Through a connection, tickers move forward only if they pass the previous block’s condition.
How connections are configured
Connections are created manually by linking blocks together on the workspace canvas.
Important: After the root block processes the initial list of tickers, it produces the first selection — the list of tickers that passed its condition. That selection becomes the input for the next block. Each block works only with the result from the previous one. This creates a step-by-step flow through the strategy. Exception: If a ticker reaches the Entry block and an entry signal is generated, it is no longer affected by previous blocks. It remains in the system until Exit conditions are met.
Each connection effectively means: “If a ticker passes this block — send it to the next block in the route.”
Connection priority
If a ticker can move into multiple branches after passing a block (i.e., several next blocks are connected), the system needs to decide which branch to send it to first. That’s what connection priority is for.
How priority works
Priority is set at the connection level, not the block level
The priority number is set manually in the UI when creating the connection
Higher number = higher priority
If a ticker satisfies two or more branches at the same time, it will follow the highest-priority connection
When you need it: - When implementing logic like: “Check the main condition first; if it doesn’t match — move to the next one.” - When logic branches from one block: Example: a ticker passes a filter, then goes either into a Long branch or a Short branch - When multiple strategies apply to the same asset
Important notes
If a ticker does not pass the next block’s condition, it won’t go there — even if that connection has high priority
If it passes multiple branches, priority is used to choose the route
One connection = one priority
Example: Priorities in action
If a ticker passes one block and matches conditions of two next blocks, QATS chooses the branch with the higher priority:
Connection from Block 1 → Block 2: priority = 5
Connection from Block 1 → Block 3: priority = 10
If both conditions are true, the ticker goes to Block 3, because that connection has the higher priority.
A branch with multiple conditions
If you need to validate several conditions, build them as sequential blocks connected one after another. Example:
Block 1: Volume > 100,000
Block 2: RSI < 30
→ The ticker must pass both blocks in sequence to move forward
Processing order
The strategy runs top-to-bottom: from root to exit
When multiple routes are possible, QATS processes higher-priority connections first
Setup examples
1) Simple pipeline Filter → Strategy → Weighting → Entry → Exit 2) Logic branching Filter ├──> Long Strategy (RSI < 30) → Long Entry → Exit └──> Short Strategy (RSI > 70) → Short Entry → Exit 3) Conditional check with priority Filter ├── (priority 10) ──> Correlation-based Strategy └── (priority 5) ───> Volume-based Strategy If the ticker matches both, it goes to the higher-priority branch first.
Final rule: type boundaries lock the route
Each next block type (Filter → Strategy → Weighting → Entry → Exit) is a logical boundary. If a ticker reaches the next block type and the condition is TRUE, it will not return to parallel or lower-priority branches. This ensures unambiguous, strictly one-way movement through the strategy tree.
QATS is not a registered broker-dealer or investment advisor. All strategies are created and managed by users. Trading involves risk, and past performance is not indicative of future results. QATS does not store or manage user funds. All trades are executed via official broker APIs. Users must be 18 years or older to use the platform.
Maurizio Vitalle 3
© 2026 Quant Algorithm Tree System Ltd.
- Workspace
- Disclaimer
- Terms of Use
- Privacy Policy
- Cookie policy