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
  • 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
IntermediateLast verified Sep 30, 2026

Order

Submits a configured Tactical order and produces a ticket for lifecycle tracking.

On this page
  1. When to use
  2. Example
  3. Follow one submission
  4. Common problems
  5. Next steps

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.

Try it here

Explore Order

Submits a configured Tactical order and produces a ticket for lifecycle tracking.

Exercise steps
  1. Change Market to Limit, then configure a limit price.
  2. Inspect Submitted: it means submission, while a later fill is handled by Await Order Event.
Event TriggerOrder
Graph preview — a diagram of the example

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.

Node facts

These facts come from the current Flow Editor node catalog.

Node type
Order
Activation role
No activation role
Category
Order
Availability
Tactical only
Modes
Tactical
Required plan
None
Behavior
Performs an action
Control inputs
1
Output data types
order Ticket

Parameters

NameInput typeRequirementDefaultOptions and constraints
Order typeSelection listRequiredmarketOptions: Market, Limit, Stop, Stop limit
SideSelection listRequiredNot setOptions: Buy, Sell
Instrument sourceSelection listRequiredinheritedOptions: Inherited, Literal, Symbol port
InstrumentTextRequired when shownNot setShown when Instrument source is literal
Quantity sourceSelection listRequiredliteralOptions: Literal, Quantity port
QuantityNumberRequired when shownNot setMinimum: 0.000001; Shown when Quantity source is literal
Limit price sourceSelection listRequired when shownliteralOptions: Literal, Limit Price port; Shown when Order type is one of limit, stopLimit
Limit priceNumberRequired when shownNot setMinimum: 0.000001; Shown when Order type is one of limit, stopLimit and Limit price source is literal
Stop price sourceSelection listRequired when shownliteralOptions: Literal, Stop Price port; Shown when Order type is one of stop, stopLimit
Stop priceNumberRequired when shownNot setMinimum: 0.000001; Shown when Order type is one of stop, stopLimit and Stop price source is literal
Time in forceSelection listOptional when shownGTCOptions: GTC, IOC, FOK, Day; Shown when Order type is one of limit, stop, stopLimit
Take profit sourceSelection listRequiredoffOptions: Off, Literal, Take Profit port
Take profitNumberOptional when shownNot setMinimum: 0.000001; Shown when Take profit source is literal
Take profit modeSelection listOptional when shownpercentOptions: Percent move, Price offset; Shown when Take profit source is not off
Stop loss sourceSelection listRequiredoffOptions: Off, Literal, Stop Loss port
Stop lossNumberOptional when shownNot setMinimum: 0.000001; Shown when Stop loss source is literal
Stop loss modeSelection listOptional when shownpercentOptions: Percent move, Price offset; Shown when Stop loss source is not off
LeverageNumberRequired1Minimum: 1; Maximum: 125; Values above 5 require Elite
Margin modeSelection listOptional when showncrossOptions: Cross, Isolated; Shown when Leverage > 1
Reduce onlyYes or noOptional when shownfalseShown when Leverage > 1
Position modeSelection listOptional when shownone-wayOptions: One-way, Hedge; Shown when Leverage > 1

Primary parameters

  • Order type
  • Side
  • Instrument source
  • Quantity source
  • Quantity
  • Leverage

Outcomes

  • Submitted
  • Denied
  • Insufficient Margin
  • Submit Failed

Data inputs

  • Signalsignal · Optional
  • SymbolText · Required when shownShown when Instrument source is dataPort
  • QuantityNumber · Required when shownShown when Quantity source is dataPort
  • Limit Priceprice · Required when shownShown when Order type is one of limit, stopLimit and Limit price source is dataPort
  • Stop Priceprice · Required when shownShown when Order type is one of stop, stopLimit and Stop price source is dataPort
  • Take ProfitNumber · Required when shownShown when Take profit source is dataPort
  • Stop LossNumber · Required when shownShown when Stop loss source is dataPort

Data outputs

  • Order Ticketorder Ticket

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.

On this page

1 / 5
  1. When to use
  2. Example
  3. Follow one submission
  4. Common problems
  5. Next steps

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

Responsible useGlossary