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

Safety Trigger

Starts a bounded auxiliary safety path when a supported measure crosses its configured threshold.

On this page
  1. When to use
  2. Example
  3. Keep the guard separate
  4. Common problems
  5. Next steps

Starts a bounded auxiliary safety path when a supported measure crosses its configured threshold.

When to use

Use it alongside the required primary Schedule Trigger when a Portfolio strategy needs a defensive response to a supported safety breach.

Example

With the primary Schedule Trigger already present, begin a defensive path when the selected safety condition breaches its limit.

Try it here

Explore Safety Trigger

Starts a bounded auxiliary safety path when a supported measure crosses its configured threshold.

Exercise steps
  1. Select Safety Trigger and change the drawdown threshold.
  2. Follow its dedicated path to Halt and inspect the all-activations cleanup policy.
Schedule TriggerHaltSafety Trigger
Graph preview — a diagram of the example

Keep the guard separate

In a scheduled Portfolio strategy, keep Schedule Trigger as the primary activation. Configure Safety Trigger to watch one supported engine metric, an operator, a threshold and an evaluation frequency. An illustrative drawdown rule is “fire when drawdown crosses the configured limit”; check the metric's unit and operator before entering a threshold. The Breach Value output can help an Alert explain what the guard observed.

Connect Safety Trigger → Alert → Halt, or the allowed direct Halt route with its required cleanup policy. The guard must not join the ranking/rebalance path and Safety Trigger → Order is not an allowed way to place a defensive trade. In a historical run the Alert is simulated; inspect the guard event and Halt outcome instead of assuming an email or a live position change.

Common problems

It is an auxiliary guard, not a primary activation. Keep the required Schedule Trigger and connect Safety Trigger only to Alert, a correctly configured Halt, or Alert followed by Halt. It cannot join the primary path.

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
Safety Trigger
Activation role
Safety activation
Category
Trigger
Availability
Portfolio only
Modes
Portfolio
Required plan
None
Behavior
Trigger
Control inputs
0
Output data types
Number, datetime

Parameters

NameInput typeRequirementDefaultOptions and constraints
Risk metricSelection listRequiredNot setOptions: $engine portfolio equity, $engine portfolio drawdown, $engine portfolio margin Used, $engine positions open count, $engine orders active count, $engine margin current leverage ratio, $engine liquidation liquidation price, $engine liquidation distance to liquidation
Breach conditionSelection listRequired>Options: >, <, >=, <=
ThresholdNumberRequiredNot setNone
Check frequencySelection listRequiredevery-barOptions: every bar, every minute, every hour

Primary parameters

  • Risk metric
  • Breach condition
  • Threshold

Outcomes

  • On Breach

Data inputs

None

Data outputs

  • Breach ValueNumber
  • Timestampdatetime

Related documentation

  • How a strategy starts and continuesUnderstand primary activation, control outcomes, and why data alone does not execute an action.
  • Build Portfolio strategiesDesign a scheduled or safety-driven graph that selects assets, calculates weights, applies limits, and rebalances.
  • RebalancerTurns valid target weights into a Portfolio rebalance result.

On this page

1 / 5
  1. When to use
  2. Example
  3. Keep the guard separate
  4. Common problems
  5. Next steps

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

Responsible useGlossary