Skip to documentation
Screebits Docs
Flow Editor
Open Screebits
  • Screebits
  • Flow Editor documentation
  • Blueprints
  • Your first steps in Screebits
  • Workspace, strategies and account
  • Get started with the Flow Editor
  • Build an RSI Momentum Alert
  • Flow Editor concepts
  • How a strategy starts and continues
  • Control and data connections
  • Nodes, parameters, outcomes, and ports
  • Plans and feature availability
  • Saves, versions, and checkpoints
  • Tactical and Portfolio strategies
  • Validation and readiness
  • Flow Editor mode guides
  • Build Portfolio strategies
  • Build Tactical strategies
  • Flow Editor guides
  • Add a Quant Hub metric
  • Configure a node
  • Configure Settings and visual preferences
  • Connect nodes
  • Create a strategy
  • Create checkpoints and restore versions
  • Reset a Flow safely
  • Debug and replay a Backtest
  • Fix validation issues
  • Use keyboard shortcuts
  • Manage variables
  • Run a Backtest
  • Save and resolve conflicts
  • Work on tablet and mobile
  • Use Quick add
  • Use the Inspector
  • Add, move, duplicate, and remove nodes
  • Flow Editor examples
  • Portfolio rebalance with risk limits
  • Tactical order and position monitoring
  • Use Backtest Center
  • Read a Backtest result
  • Compare and export Backtests
  • Explore Quant Hub
  • Metric parameters, charts and overlays
  • Flow Editor node reference
  • Await Order Event
  • Flow Editor troubleshooting
  • Troubleshoot activation and validation
  • Troubleshoot Backtests and replay
  • Troubleshoot compact layouts
  • Troubleshoot connections and data types
  • Troubleshoot plans and locked features
  • Troubleshoot Quant Hub in the Flow Editor
  • Troubleshoot save, offline, and conflicts
  • Backtests and responsible use
  • Flow Editor glossary
  1. Screebits
  2. /Flow Editor documentation
  3. /Flow Editor node reference
  4. /Await Order Event
IntermediateLast verified Sep 30, 2026

Await Order Event

Waits for lifecycle events associated with a submitted Order Ticket.

On this page
  1. When to use
  2. Example
  3. Distinguish submission from completion
  4. Common problems
  5. Next steps

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.

Try it here

Explore Await Order Event

Waits for lifecycle events associated with a submitted Order Ticket.

Exercise steps
  1. Change the timeout unit from bars to minutes.
  2. Inspect the Order Ticket input and compare Accepted, Filled and Timeout.
Event TriggerOrderAwait Order Event
Graph preview — a diagram of the example

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.

Node facts

These facts come from the current Flow Editor node catalog.

Node type
Await Order Event
Activation role
Continues an existing path
Category
Order
Availability
Tactical only
Modes
Tactical
Required plan
None
Behavior
Waits for an event
Control inputs
1
Output data types
order Result, price, Number

Parameters

NameInput typeRequirementDefaultOptions and constraints
Timeout valueNumberRequired1Minimum: 1; Maximum: 10000; Whole numbers only; Maximum depends on Timeout unit
Timeout unitSelection listRequiredbarsOptions: Bars, Seconds, Minutes, Hours

Primary parameters

  • Timeout value
  • Timeout unit

Outcomes

  • Accepted
  • Triggered
  • Filled
  • Take Profit
  • Stop Loss
  • Expired
  • Canceled
  • Rejected
  • Timeout

Data inputs

  • Order Ticketorder Ticket · Required

Data outputs

  • Order Resultorder Result
  • Fill Priceprice
  • Fill QuantityNumber

Related documentation

  • OrderSubmits a configured Tactical order and produces a ticket for lifecycle tracking.
  • Position MonitorObserves an open position and branches on updates, exits, and closure.
  • Cancel OrdersRequests cancellation for one pending order or for open strategy orders.

On this page

1 / 5
  1. When to use
  2. Example
  3. Distinguish submission from completion
  4. Common problems
  5. Next steps

Practical guidance for strategies, historical simulations and metric research in Screebits.

Responsible useGlossary