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

Rebalance Result Field

Extracts one field from a rebalance result.

On this page
  1. When to use
  2. Example
  3. Compare target and result
  4. Common problems
  5. Next steps

Extracts one field from a rebalance result.

When to use

Use it when a downstream Alert or comparison needs a scalar detail after Rebalancer.

Example

Extract the number of generated changes and include it in a completion message.

Try it here

Explore Rebalance Result Field

Extracts one field from a rebalance result.

Exercise steps
  1. Choose a different field in Inspector.
  2. Observe how the active output and its type change; the connected input keeps its structured value.
Schedule TriggerRebalancerWeight CalculatorUniverseRebalance Result Field
Graph preview — a diagram of the example

Compare target and result

Connect Rebalancer: Result to the input and select Target Weights to see the requested allocation or Actual Weights to inspect the reported outcome. In a two-asset target of 50%/50%, the reported actual weights may differ because of tolerance, minimum trade size, constraints, prices or skipped assets. Select Orders Generated for a count and Skipped Assets for names rather than inferring action from the target vector alone. A zero-order or No Change run is not the same as a failed data connection; read the Rebalancer control outcome alongside these fields.

Common problems

Use it only on a path where a result is available. Empty-universe, constraint, and no-change outcomes need their own 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
Rebalance Result Field
Activation role
No activation role
Category
Field
Availability
Portfolio only
Modes
Portfolio
Required plan
None
Behavior
Transforms a value
Control inputs
0
Output data types
weight Vector, Number, string List, leverage Metrics

Parameters

NameInput typeRequirementDefaultOptions and constraints
Rebalance result fieldSelection listRequiredactualTurnoverOptions: Target weights, Actual weights, Actual turnover, Orders generated, Skipped assets, Leverage metrics

Primary parameters

  • Rebalance result field

Outcomes

None

Data inputs

  • Rebalance Resultrebalance Result · Required

Data outputs

  • Target Weightsweight VectorShown when Rebalance result field is targetWeights
  • Actual Weightsweight VectorShown when Rebalance result field is actualWeights
  • Actual TurnoverNumberShown when Rebalance result field is actualTurnover
  • Orders GeneratedNumberShown when Rebalance result field is ordersGenerated
  • Skipped Assetsstring ListShown when Rebalance result field is skippedAssets
  • Leverage Metricsleverage MetricsShown when Rebalance result field is leverageMetrics

Related documentation

  • RebalancerTurns valid target weights into a Portfolio rebalance result.
  • AlertRecords an Alert message on a control outcome; Backtests simulate delivery.
  • Portfolio rebalance with risk limitsUnderstand a Portfolio pattern that filters an asset universe, calculates target weights, applies constraints, and rebalances.

On this page

1 / 5
  1. When to use
  2. Example
  3. Compare target and result
  4. Common problems
  5. Next steps

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

Responsible useGlossary