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 Constraint
  • 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 Constraint
IntermediateLast verified Sep 30, 2026

Leverage Constraint

Checks or adjusts target weights against configured leverage limits.

On this page
  1. When to use
  2. Example
  3. Choose adjustment or rejection
  4. Common problems
  5. Next steps

Checks or adjusts target weights against configured leverage limits.

When to use

Use it in eligible Portfolio graphs before rebalancing leveraged allocations.

Example

Pass candidate weights through the constraint and send adjusted weights to Rebalancer when the configured behavior allows adjustment.

Try it here

Explore Leverage Constraint

Checks or adjusts target weights against configured leverage limits.

Exercise steps
  1. Change Max gross leverage and the node role.
  2. Compare Adjusted Weights with the Passed, Adjusted and Violated outcomes.
Schedule TriggerWeight CalculatorUniverseLeverage Constraint
Graph preview — a diagram of the example

Choose adjustment or rejection

Feed candidate Weights and, where needed, Current Leverage Metrics into the node. Suppose a candidate implies gross leverage 1.4 while Max gross leverage is 1. In the default Adjust weights role with a supported proportional-scale strategy, inspect the Adjusted Weights and Violations data outputs; this role has no control outcome. The target may be reduced rather than accepted unchanged. In Guard role, route Passed, Adjusted (when the adjustment strategy permits it), and Violated separately. The exact result also depends on net and per-position caps, so a single illustrative ratio cannot establish that every constraint passes. Connect the resulting weights, not the original candidate, to the next stage when adjustment is intended.

Common problems

Availability can depend on plan. The default adjustWeights role is data-only: it produces Adjusted Weights and Violations. Only the guard role exposes Passed, Adjusted and Violated control outcomes. Do not confuse the Violations data output with the Violated control branch.

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 Constraint
Activation role
No activation role
Category
Portfolio
Availability
Portfolio only
Modes
Portfolio
Required plan
Pro
Behavior
Transforms a value
Control inputs
1
Output data types
weight Vector, string List

Parameters

NameInput typeRequirementDefaultOptions and constraints
roleSelection listRequiredadjustWeightsOptions: adjust Weights, guard
Max gross leverageNumberRequired1Minimum: 0.000001; Maximum: 10
Max net leverageNumberOptionalNot setMinimum: 0.000001; Maximum: 10
Max position leverageNumberOptionalNot setMinimum: 0.000001; Maximum: 10
Adjustment strategySelection listRequiredproportional_scaleOptions: proportional scale, largest first, Reject

Primary parameters

  • role
  • Max gross leverage
  • Max net leverage
  • Max position leverage

Outcomes

  • PassedShown when role is guard
  • AdjustedShown when role is guard and Adjustment strategy is not reject
  • ViolatedShown when role is guard

Data inputs

  • Weightsweight Vector · Required
  • Current Leverage Metricsleverage Metrics · Optional

Data outputs

  • Adjusted Weightsweight Vector
  • Violationsstring List

Related documentation

  • Portfolio ConstraintChecks candidate weights against configured portfolio limits.
  • Leverage Metrics FieldExtracts one field from portfolio leverage metrics.
  • RebalancerTurns valid target weights into a Portfolio rebalance result.

On this page

1 / 5
  1. When to use
  2. Example
  3. Choose adjustment or rejection
  4. Common problems
  5. Next steps

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

Responsible useGlossary