Skip to documentation
Screebits Docs
Flow Editor
Open Screebits
  • Screebits
  • Flow Editor documentation
  • Blueprints
  • Your first steps in Screebits
  • Workspace, strategies and account
  • Get started with the Flow Editor
  • Build an RSI Momentum Alert
  • Flow Editor concepts
  • How a strategy starts and continues
  • Control and data connections
  • Nodes, parameters, outcomes, and ports
  • Plans and feature availability
  • Saves, versions, and checkpoints
  • Tactical and Portfolio strategies
  • Validation and readiness
  • Flow Editor mode guides
  • Build Portfolio strategies
  • Build Tactical strategies
  • Flow Editor guides
  • Add a Quant Hub metric
  • Configure a node
  • Configure Settings and visual preferences
  • Connect nodes
  • Create a strategy
  • Create checkpoints and restore versions
  • Reset a Flow safely
  • Debug and replay a Backtest
  • Fix validation issues
  • Use keyboard shortcuts
  • Manage variables
  • Run a Backtest
  • Save and resolve conflicts
  • Work on tablet and mobile
  • Use Quick add
  • Use the Inspector
  • Add, move, duplicate, and remove nodes
  • Flow Editor examples
  • Portfolio rebalance with risk limits
  • Tactical order and position monitoring
  • Use Backtest Center
  • Read a Backtest result
  • Compare and export Backtests
  • Explore Quant Hub
  • Metric parameters, charts and overlays
  • Flow Editor node reference
  • Gate
  • Flow Editor troubleshooting
  • Troubleshoot activation and validation
  • Troubleshoot Backtests and replay
  • Troubleshoot compact layouts
  • Troubleshoot connections and data types
  • Troubleshoot plans and locked features
  • Troubleshoot Quant Hub in the Flow Editor
  • Troubleshoot save, offline, and conflicts
  • Backtests and responsible use
  • Flow Editor glossary
  1. Screebits
  2. /Flow Editor documentation
  3. /Flow Editor node reference
  4. /Gate
IntermediateLast verified Sep 30, 2026

Gate

Combines control arrivals according to a configured pass rule.

On this page
  1. When to use
  2. Example
  3. Wait for the intended arrivals
  4. Common problems
  5. Next steps

Combines control arrivals according to a configured pass rule.

When to use

Use it when several control branches must be coordinated before the graph continues.

Example

Wait for the required upstream arrivals, then continue through Pass; handle Blocked separately.

Try it here

Explore Gate

Combines control arrivals according to a configured pass rule.

Exercise steps
  1. Compare AND and OR with the two connected control paths.
  2. Inspect arrival controls and remember that the graph alone does not execute them.
Event TriggerDelayGate
Graph preview — a diagram of the example

Wait for the intended arrivals

Connect two control branches A and B to Gate and choose AND. In per-execution scope, a single A arrival is not both branches; once A and B have arrived for the same execution, Pass can continue. OR asks whether any qualifying branch arrived instead. If you use the stateful scope or a timeout wait mode, read the memory and timeout settings because arrivals may be accumulated or released differently. Route Blocked to a safe handling path. The Arrival Count data output helps diagnose what was seen; it is not a third control input.

Common problems

Gate joins control, not arbitrary data. Configure the arrival rule deliberately and avoid using it to create a cycle.

Next steps

Review the generated Parameters, Outcomes, and Data Ports on this page, then open the related guides for the complete workflow.

Node facts

These facts come from the current Flow Editor node catalog.

Node type
Gate
Activation role
No activation role
Category
Condition
Availability
Tactical and Portfolio
Modes
Tactical and Portfolio
Required plan
None
Behavior
Makes a decision
Control inputs
8
Output data types
Number

Parameters

NameInput typeRequirementDefaultOptions and constraints
Branch ruleSelection listRequiredANDOptions: All branches, Any branch, Majority, At least N
Required arrivalsNumberOptional when shownNot setMinimum: 1; Maximum: 8; Shown when Branch rule is AT_LEAST_N
Evaluation scopeSelection listRequiredper-executionOptions: per execution, Remember recent arrivals
Memory windowNumberOptional when shownNot setMinimum: 1; Maximum: 100; Shown when Evaluation scope is stateful
Wait modeSelection listRequiredall_arrivedOptions: all arrived, Use timeout
TimeoutNumberOptional when shown5000Minimum: 1; Maximum: 86400000; Shown when Wait mode is timeout

Primary parameters

  • Branch rule
  • Required arrivals
  • Wait mode

Outcomes

  • Pass
  • Blocked

Data inputs

None

Data outputs

  • Arrival CountNumber
  • Total InputsNumber

Related documentation

  • Control and data connectionsUse control connections to continue execution and data connections to pass compatible values.
  • Join / Data MergeConverges control branches as a Join or combines compatible data inputs as a Data Merge.
  • Fix validation issuesUse the validation area to locate a blocking problem, correct it, and confirm that it is resolved.

On this page

1 / 5
  1. When to use
  2. Example
  3. Wait for the intended arrivals
  4. Common problems
  5. Next steps

Practical guidance for strategies, historical simulations and metric research in Screebits.

Responsible useGlossary