Delay
Waits for a configured duration before continuing the current path.
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.
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.