Choose a stable condition
Use a result field that directly represents the decision, not a loosely worded message that may change. For example, test whether a record identifier exists or whether the returned change count is greater than zero when that is the intended business rule.
Handle missing or malformed output explicitly. A missing field should not silently be treated as success; route it to an error or review path with enough context to find the source step.
Keep each branch understandable
Name branches after their meaning and keep actions for each outcome close to the condition that selects them. When two outcomes share work, join them only after recording the state that explains why each path was taken.
Exercise every branch with representative inputs, including an empty result and a failure. Inspect run history to confirm the evaluated condition and final action; this catches incorrect field paths and assumptions about value types.