Order Result Field
Extracts one field from an order execution result.
Extracts one field from an order execution result.
When to use
Use it after an order lifecycle event when a scalar such as status, fill price, or quantity is needed.
Example
Extract the fill price from a filled Order Result and include it in an Alert.
Read the lifecycle result
Feed the Order Result from Await Order Event into this extractor. On a confirmed Filled route, selecting Fill Price or Fill Qty gives the corresponding execution value, while Status says which lifecycle state was reported. For example, a filled quantity of 2 at price 101 can be passed to logic that needs those actual values. On Rejected, Canceled, or Timeout, do not assume the fill fields are populated merely because the extractor exposes their possible ports. Choose a field that matches the outcome and verify it in the run trace.
Common problems
Not every lifecycle outcome provides the same details. Handle rejected, canceled, and timeout paths separately.
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.
- AlertRecords an Alert message on a control outcome; Backtests simulate delivery.
- Tactical order and position monitoringUnderstand a Tactical pattern that sizes an order, checks margin, tracks its lifecycle, and monitors the position.