Delays and conditional behavior
Conditions choose whether later work should run. Delays wait for a defined interval. Neither should hide missing data or an unclear trigger.
On this page2

Add control flow
- Add a
Conditionstep and describe the decision in plain language. - Reference only trigger data or outputs from steps that run earlier.
- Add a
Delaywith an explicit interval and unit when work must wait. - Use a loop only with a bounded item source and at least one nested step.
- Test both the matching and non-matching condition paths.
Expected result
Each test follows the expected branch, delays for the configured interval, and never reads an output that does not exist. For long or calendar-based waiting, use a schedule trigger rather than keeping an interactive task open.