Tactical order and position monitoring
Understand a Tactical pattern that sizes an order, checks margin, tracks its lifecycle, and monitors the position.
This example is a composition pattern, not a ready-made trading recommendation.
Goal
After a Tactical signal matches, calculate a position size, check available margin, submit an order, wait for lifecycle events, and monitor an opened position.
Suggested structure
- Event Trigger starts the control path.
- Data Source and Indicator provide signal data.
- Condition selects Match or No Match.
- Position Sizer calculates quantity from explicit risk inputs.
- Margin Check handles Sufficient and Insufficient separately.
- Order submits the configured request and produces an Order Ticket.
- Await Order Event handles filled, rejected, canceled, expired, and timeout outcomes.
- Position Monitor follows an open position and handles update, exit, and closure outcomes.
Use Order Ticket Field or Order Result Field only when you need a scalar value from their structured output.
Safety branches
Do not connect only the successful path. Add an Alert, Cancel Orders, Halt, or another appropriate recovery for denied submission, insufficient margin, timeout, and rejected outcomes.
Verify
Check every required input, resolve validation, save, and review Backtest execution assumptions and costs. Simulated results do not guarantee live results.
Related documentation
- Build Tactical strategiesDesign an event-driven graph with one primary trigger, explicit control branches, and typed market data.
- OrderSubmits a configured Tactical order and produces a ticket for lifecycle tracking.
- Position MonitorObserves an open position and branches on updates, exits, and closure.