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

Cancel Result Field

Extracts one field from the result of a cancellation request.

On this page
  1. When to use
  2. Example
  3. Account for every request
  4. Common problems
  5. Next steps

Extracts one field from the result of a cancellation request.

When to use

Use it when a downstream decision or message needs a scalar cancellation detail.

Example

Extract the cancellation status and include it in an operational Alert.

Try it here

Explore Cancel Result Field

Extracts one field from the result of a cancellation request.

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 TriggerCancel OrdersCancel Result Field
Graph preview — a diagram of the example

Account for every request

Connect Cancel Orders: Cancel Result and extract Requested Count, Canceled Count, or Not Canceled Count. If a simulated request covers three matching orders and reports two canceled and one not canceled, the latter still needs investigation; it may have changed state before confirmation. Extract Client Order ID only when the cancellation scope identifies a particular ticket. The result describes the cancellation request, not a reversal of a previous fill. Read Cancel Orders' control outcome as well as the selected count.

Common problems

A requested cancellation can produce a not-canceled result. Do not assume the order was canceled until the connected outcome confirms it.

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
Cancel 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, Number, datetime

Parameters

NameInput typeRequirementDefaultOptions and constraints
Cancel result fieldSelection listRequiredstatusOptions: Status, Scope, Client order id, Side, Requested count, Canceled count, Not canceled count, Reason, Confirmed at

Primary parameters

  • Cancel result field

Outcomes

None

Data inputs

  • Cancel Resultcancel Result · Required

Data outputs

  • StatusTextShown when Cancel result field is status
  • ScopeTextShown when Cancel result field is scope
  • Client Order IdTextShown when Cancel result field is clientOrderId
  • SideTextShown when Cancel result field is side
  • Requested CountNumberShown when Cancel result field is requestedCount
  • Canceled CountNumberShown when Cancel result field is canceledCount
  • Not Canceled CountNumberShown when Cancel result field is notCanceledCount
  • ReasonTextShown when Cancel result field is reason
  • Confirmed AtdatetimeShown when Cancel result field is confirmedAt

Related documentation

  • Cancel OrdersRequests cancellation for one pending order or for open strategy orders.
  • 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. Account for every request
  4. Common problems
  5. Next steps

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

Responsible useGlossary