Order
Submits a configured Tactical order and produces a ticket for lifecycle tracking.
Submits a configured Tactical order and produces a ticket for lifecycle tracking.
When to use
Use it only after signal, sizing, risk, and margin decisions are complete.
Example
Continue from Margin Check Sufficient to Order, then pass the Order Ticket to Await Order Event.
Follow one submission
In a Tactical graph, let a signal and sizing path determine the instrument, side and quantity. Configure Order's source choices deliberately: a fixed quantity uses its literal field; a computed quantity requires the numeric Quantity data input. A limit or stop variant needs its corresponding price source and value. Route the Sufficient control outcome of Margin Check into Order only after reviewing the estimate. The estimate does not guarantee the later submission.
When Order takes Submitted, connect its Order Ticket data output to Await Order Event and its Submitted control outcome to that continuation. Submitted means an order was accepted for tracking, not that it filled. Keep distinct branches for Denied, Insufficient Margin, and Submit Failed; a downstream Position Monitor belongs after a confirmed filled event, not directly after Submitted. See the Tactical lifecycle example for the complete path.
Common problems
Handle denied, insufficient-margin, and submission-failure outcomes. A submitted ticket is not the same as a completed fill.
Next steps
Review the generated Parameters, Outcomes, and Data Ports on this page, then open the related guides for the complete workflow.
Related documentation
- Margin CheckChecks a proposed Tactical order against available margin before submission.
- Await Order EventWaits for lifecycle events associated with a submitted Order Ticket.
- Tactical order and position monitoringUnderstand a Tactical pattern that sizes an order, checks margin, tracks its lifecycle, and monitors the position.