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

Delay

Waits for a configured duration before continuing the current path.

On this page
  1. When to use
  2. Example
  3. Preserve the activation
  4. Common problems
  5. Next steps

Waits for a configured duration before continuing the current path.

When to use

Use it when a forward path should pause before the next supported action.

Example

Wait briefly before checking an order lifecycle state or sending a follow-up Alert.

Try it here

Explore Delay

Waits for a configured duration before continuing the current path.

Exercise steps
  1. Change the duration and compare bars with time units.
  2. Follow the Next connection point; a delay continues an existing activation.
Event TriggerDelay
Graph preview — a diagram of the example

Preserve the activation

Connect Event Trigger → Delay → Alert and set Duration 2, Unit Bars. The Alert continues from Delay's Next outcome after the selected two-bar wait in that activation's context. This is different from a two-second wait: bars depend on the relevant market series and timeframe. A delay does not create a new signal, turn an unfilled order into a fill, or provide a market value. For order lifecycle tracking use Await Order Event with a ticket and explicit timeout; use Delay when the design genuinely calls for postponing control.

Common problems

Delay does not make graph cycles valid and is not a scheduling trigger. Keep duration and unit explicit.

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
Delay
Activation role
Continues an existing path
Category
Action
Availability
Tactical and Portfolio
Modes
Tactical and Portfolio
Required plan
None
Behavior
Waits for an event
Control inputs
1
Output data types
None

Parameters

NameInput typeRequirementDefaultOptions and constraints
DurationNumberRequired1Minimum: 1; Whole numbers only; Maximum depends on Unit
UnitSelection listRequiredbarsOptions: Bars, Seconds, Minutes, Hours

Primary parameters

  • Duration
  • Unit

Outcomes

  • After Delay

Data inputs

None

Data outputs

None

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.
  • How a strategy starts and continuesUnderstand primary activation, control outcomes, and why data alone does not execute an action.

On this page

1 / 5
  1. When to use
  2. Example
  3. Preserve the activation
  4. Common problems
  5. Next steps

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

Responsible useGlossary