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
  • Order Result Field
  • 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. /Order Result Field
IntermediateLast verified Sep 30, 2026

Order Result Field

Extracts one field from an order execution result.

On this page
  1. When to use
  2. Example
  3. Read the lifecycle result
  4. Common problems
  5. Next steps

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.

Try it here

Explore Order Result Field

Extracts one field from an order execution result.

Exercise steps
  1. Choose a different field in Inspector.
  2. Observe how the active output and its type change; the connected input keeps its structured value.
Event TriggerAwait Order EventOrderOrder Result Field
Graph preview — a diagram of the example

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.

Node facts

These facts come from the current Flow Editor node catalog.

Node type
Order Result Field
Activation role
No activation role
Category
Field
Availability
Tactical only
Modes
Tactical
Required plan
None
Behavior
Transforms a value
Control inputs
0
Output data types
Text, price, Number, datetime

Parameters

NameInput typeRequirementDefaultOptions and constraints
Order result fieldSelection listRequiredstatusOptions: Status, Fill price, Filled quantity, Commission, Fill timestamp, Client order id, Side

Primary parameters

  • Order result field

Outcomes

None

Data inputs

  • Order Resultorder Result · Required

Data outputs

  • StatusTextShown when Order result field is status
  • Fill PricepriceShown when Order result field is fillPrice
  • Fill QtyNumberShown when Order result field is fillQty
  • CommissionNumberShown when Order result field is commission
  • Fill TimestampdatetimeShown when Order result field is fillTimestamp
  • Client Order IdTextShown when Order result field is clientOrderId
  • SideTextShown when Order result field is side

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.

On this page

1 / 5
  1. When to use
  2. Example
  3. Read the lifecycle result
  4. Common problems
  5. Next steps

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

Responsible useGlossary