Position Monitor
Observes an open position and branches on updates, exits, and closure.
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.
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.
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.