Conditions, branches and waiting
Connections define execution order. A workflow follows one selected path at a time; a branch does not start parallel work. Every required outcome must connect to a valid continuation, and converging branches use an explicit Join.
Conditionsโ
Conditions belong to If/Else. Ordinary action steps have no embedded condition. To run one action conditionally and then continue, place it on the matching If/Else path and reconnect both paths through Join to the shared continuation.
Conditions compare a supported field with a value. Use an all or any group for up to ten comparisons. Available operators depend on the field's type. Missing or null values match only the empty check, so explicitly consider absent data.
To continue only when a condition matches, connect the otherwise path to End. For example, after a status-change trigger, create a review Task on the matching path and end the other path. Both outcomes finish successfully, and earlier effects remain.
If/Else and Joinโ
If/Else selects either its true or false connection. Both paths must be configured. Join reconnects alternatives that should share subsequent steps. It adds no result fields and is not a barrier for parallel work.
After a Join, data mappings can use outputs from either earlier branch. A skipped source supplies null or its binding default. An Update Task target still needs a Create Task or Read Task step that runs on every incoming path, because the update requires an existing Task receipt.
Waitโ
Choose a duration or a timestamp. A duration is measured when the step is reached. A timestamp can be fixed or mapped from a supported date/time output and must identify an instant with a timezone offset.
Wait is durable: it remains part of the same run through worker interruptions. A reached timestamp in the past needs no further waiting. Future waits are bounded to 30 days. A missing, invalid or out-of-range timestamp can fail the step; a timestamp-looking ordinary string is not enough to establish a date/time contract.
Some other actions support a delay before their operation. Use Wait when time should be a distinct, inspectable step. Preview reports timing without creating a timer.
Endโ
End finishes the selected path successfully. It has no configuration or outputs. Use it for deliberate completion, including rejected or expired business outcomes. Ending a run does not undo earlier Tasks or record changes.
For decisions made by people, see Approvals and human questions.