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

Leverage Monitor

Emits margin-warning and liquidation-risk branches for a leveraged position.

On this page
  1. When to use
  2. Example
  3. Route warning and risk separately
  4. Common problems
  5. Next steps

Emits margin-warning and liquidation-risk branches for a leveraged position.

When to use

Use it when an eligible Tactical path needs active leverage-risk monitoring.

Example

Route Margin Warning to an Alert and Liquidation Risk to a defensive action.

Try it here

Explore Leverage Monitor

Emits margin-warning and liquidation-risk branches for a leveraged position.

Exercise steps
  1. Change warning and liquidation-risk thresholds.
  2. Compare the two outcomes and inspect the Margin State output.
Event TriggerLeverage Monitor
Graph preview — a diagram of the example

Route warning and risk separately

Set the monitoring frequency and thresholds after checking the unit of the account's margin or liquidation-risk measure. In a recorded Tactical run, a state crossing Warning threshold can follow On Margin Warning to an Alert. A more severe state crossing Liquidation risk threshold follows On Liquidation Risk to a defensive path. Connect the Margin State data output to Margin State Field when you need the observed amount or ratio in a diagnostic message. Neither outcome means that a liquidation has already executed, and a monitoring branch is not a substitute for the pre-order Margin Check.

Common problems

Availability can depend on the current plan. Connect both risk outcomes and do not use its data output as a substitute for control handling.

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
Leverage Monitor
Activation role
Continues an existing path
Category
Trigger
Availability
Tactical only
Modes
Tactical
Required plan
Pro
Behavior
Trigger
Control inputs
1
Output data types
margin State

Parameters

NameInput typeRequirementDefaultOptions and constraints
Margin warning levelNumberRequired0.5Minimum: 0; Maximum: 1
Liquidation risk levelNumberRequired0.8Minimum: 0; Maximum: 1
Check frequencySelection listRequiredevery-barOptions: every bar, every minute, every hour

Primary parameters

  • Margin warning level
  • Liquidation risk level

Outcomes

  • Margin Warning
  • Liquidation Risk

Data inputs

None

Data outputs

  • Margin Statemargin State

Related documentation

  • Margin State FieldExtracts one field from a margin state value.
  • Position MonitorObserves an open position and branches on updates, exits, and closure.
  • Troubleshoot plans and locked featuresDistinguish a plan requirement from a validation problem, catalog restriction, or read-only state.

On this page

1 / 5
  1. When to use
  2. Example
  3. Route warning and risk separately
  4. Common problems
  5. Next steps

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

Responsible useGlossary