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
  • Halt
  • 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. /Halt
IntermediateLast verified Sep 30, 2026

Halt

Stops the current trigger path or all active trigger paths according to its configuration.

On this page
  1. When to use
  2. Example
  3. Decide what stopping means
  4. Common problems
  5. Next steps

Stops the current trigger path or all active trigger paths according to its configuration.

When to use

Use it for an intentional terminal outcome such as a safety stop or unrecoverable branch.

Example

After a critical safety outcome, halt the relevant path with the required cleanup behavior.

Try it here

Explore Halt

Stops the current trigger path or all active trigger paths according to its configuration.

Exercise steps
  1. Compare Current activation and All activations.
  2. Change the cleanup policy and read what it will close or leave in place.
Event TriggerHalt
Graph preview — a diagram of the example

Decide what stopping means

Connect a critical branch to Halt and choose whether the current activation or all activations should stop. Then set the required cleanup policy deliberately: cancel open orders, cancel and close exposure, or leave runtime state as it is. For a Portfolio Safety Trigger guard, only the allowed Halt configuration is valid; check validation before assuming an all-activations cleanup is available on that route. Halt ends control flow, but cleanup actions can have their own outcomes and cannot undo an earlier fill. Verify the recorded stop and affected orders or positions in the run result.

Common problems

Halt is terminal. Confirm whether the scope is the current path or all paths, and review pending-order cleanup before relying on it.

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
Halt
Activation role
No activation role
Category
Flow
Availability
Tactical and Portfolio
Modes
Tactical and Portfolio
Required plan
None
Behavior
Ends a path
Control inputs
1
Output data types
None

Parameters

NameInput typeRequirementDefaultOptions and constraints
What to stopSelection listRequiredcurrent-activationOptions: current activation, all activations
Risk cleanupSelection listRequiredcancel-all-ordersOptions: cancel all orders, cancel and close, leave as is

Primary parameters

  • What to stop
  • Risk cleanup

Outcomes

None

Data inputs

None

Data outputs

None

Related documentation

  • Safety TriggerStarts a bounded auxiliary safety path when a supported measure crosses its configured threshold.
  • Cancel OrdersRequests cancellation for one pending order or for open strategy orders.
  • Tactical order and position monitoringUnderstand a Tactical pattern that sizes an order, checks margin, tracks its lifecycle, and monitors the position.

On this page

1 / 5
  1. When to use
  2. Example
  3. Decide what stopping means
  4. Common problems
  5. Next steps

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

Responsible useGlossary