okta-workflows-branching

Okta Workflows performs no implicit type coercion in comparisons, so comparing '6' as Text with 30 as Number runs an alphabetical text comparison and returns false. Set both value A and value B to the same type in the card dropdowns, or coerce values upstream with a Number or Text conversion card.

The If/Else card supports only one condition. Use True/False Compare cards feeding an And, Or, Not, or XNOR card to produce a single boolean, then pass that into If/Else, or use an If/ElseIf card which evaluates multiple conditions top-down.

Okta guidance recommends nesting no more than 3 If/ElseIf statements because deeper nesting is hard to understand and debug. Flatten the logic into a single If/ElseIf with multiple conditions or precompute a boolean with True/False logic cards.

Outputs from inside a branch are undefined whenever a different branch runs, so Workflows blocks dragging them to cards after the If/ElseIf. Use the block's Create Outputs or View Outputs feature to assign values after whichever branch completes.

No. Inside If/ElseIf or If Error blocks, Return and Continue If act as anonymous helper flows, so execution proceeds to the step after the block instead of halting. Use Return Error, Return Error If, or a Continue If placed outside the block to actually stop the flow.