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

Position Monitor

Observes an open position and branches on updates, exits, and closure.

On this page
  1. When to use
  2. Example
  3. Monitor only an established position
  4. Common problems
  5. Next steps

Observes an open position and branches on updates, exits, and closure.

When to use

Use it after a position has been established and the strategy needs ongoing exit or status logic.

Example

Monitor a filled position, send updates to one branch, and handle closure on another.

Try it here

Explore Position Monitor

Observes an open position and branches on updates, exits, and closure.

Exercise steps
  1. Compare trailing stop, break even and time stop.
  2. Inspect which parameters appear for each monitoring mode.
Event TriggerAwait Order EventOrderPosition Monitor
Graph preview — a diagram of the example

Monitor only an established position

Route a confirmed Filled order-event branch to the monitoring logic, and supply the required Position data input from a compatible position context. A fill price alone is not a Position payload. Choose Trailing stop, Break even, or Time stop, then complete only the settings active for that mode. For example, a time stop configured for ten bars can report updates while the position remains open and an exit when its condition is met. On Update, On Exit, and Position Closed describe different lifecycle observations; give each a deliberate downstream path. Inspect Current Stop and Unrealized PnL as data, not as proof of a close.

Common problems

Provide a valid open position context. Do not assume every update means an exit, and handle closure explicitly.

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
Position Monitor
Activation role
Continues an existing path
Category
Action
Availability
Tactical only
Modes
Tactical
Required plan
None
Behavior
Performs an action
Control inputs
1
Output data types
price, Number

Parameters

NameInput typeRequirementDefaultOptions and constraints
Monitor typeSelection listRequiredtrailingStopOptions: Trailing stop, Break even, Time stop
Trailing methodSelection listOptional when shownpercentOptions: Fixed distance, ATR based, Percent; Shown when Monitor type is trailingStop
Trailing distanceNumberOptional when shown2Minimum: 0.000001; Shown when Monitor type is trailingStop
ATR periodNumberOptional when shown14Minimum: 1; Whole numbers only; Shown when Monitor type is trailingStop and Trailing method is atr
Break-even triggerNumberOptional when shown1Minimum: 0.000001; Shown when Monitor type is breakEven
Break-even offsetNumberOptional when shown0.1Minimum: 0; Shown when Monitor type is breakEven
Time-stop unitSelection listOptional when shownbarsOptions: Bars, Ticks; Shown when Monitor type is timeStop
Max barsNumberOptional when shown10Minimum: 1; Whole numbers only; Shown when Monitor type is timeStop and Time-stop unit is bars
Max ticksNumberOptional when shown10Minimum: 1; Whole numbers only; Shown when Monitor type is timeStop and Time-stop unit is ticks

Primary parameters

  • Monitor type
  • Trailing method
  • Trailing distance
  • Time-stop unit
  • Max bars
  • Max ticks

Outcomes

  • On Exit
  • On Update
  • Position Closed

Data inputs

  • Positionposition · Required
  • Barbar · Optional when shownShown when Monitor type is not timeStop or Time-stop unit is bars

Data outputs

  • Current StoppriceShown when Monitor type is trailingStop or Monitor type is breakEven
  • Unrealized PnLNumber
  • Bars Since EntryNumberShown when Monitor type is not timeStop or Time-stop unit is bars
  • Ticks Since EntryNumberShown when Monitor type is timeStop and Time-stop unit is ticks

Related documentation

  • Await Order EventWaits for lifecycle events associated with a submitted Order Ticket.
  • Leverage MonitorEmits margin-warning and liquidation-risk branches for a leveraged position.
  • 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. Monitor only an established position
  4. Common problems
  5. Next steps

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

Responsible useGlossary