Await Order Event
Waits for lifecycle events associated with a submitted Order Ticket.
Waits for lifecycle events associated with a submitted Order Ticket.
When to use
Use it after Order when the graph must distinguish accepted, filled, rejected, expired, canceled, or timeout states.
Example
Pass the Order Ticket from Order, continue a filled path to Position Monitor, and route timeout to Cancel Orders.
Distinguish submission from completion
Connect Order: Submitted as the control predecessor and Order: Order Ticket as the data input to Await Order Event. Set a finite timeout in the selected unit. The continuation observes the lifecycle of that ticket and exposes separate outcomes such as Accepted, Filled, Rejected, Canceled, and Timeout. Use Filled, together with the resulting order data, for logic that requires a fill. Accepted or Triggered alone does not provide that guarantee.
For a timeout, route to an explicit recovery such as Cancel Orders and inspect its result. Cancellation is another request: an order may already have filled or may not be cancelable. Keep rejected, canceled and expired paths distinct from Filled. A consumer of Fill Price or Fill Quantity should be reached only on a path where those values are meaningful.
Common problems
Connect the ticket from the same order path. Handle timeout and unsuccessful outcomes instead of waiting indefinitely.
Next steps
Review the generated Parameters, Outcomes, and Data Ports on this page, then open the related guides for the complete workflow.