Contacts routing to the wrong branch
Review the condition operators
Check the condition values
VIP Customer, the condition must match that exact string — vip customer will not match with the equals operator.Verify AND vs OR logic
Test with a known contact
Empty field handling
Nested conditions not evaluating correctly
Flatten complex logic when possible
Check each level independently
Review the execution logs
Custom field type mismatches
Custom fields have specific data types that affect how conditions are evaluated. A mismatch between the field type and the condition operator will cause unexpected results.Confirm the field type
Update the condition operator
Re-test after changes
Best practices
- Use descriptive branch names (e.g., “Has email — send nurture” instead of “Branch 1”) so the logic is clear at a glance
- Add an Else catch-all branch that logs or tags contacts who do not match any condition, so you can identify gaps
- Document complex condition logic in the workflow’s internal notes
- Test every branch path before publishing
FAQs
Can I use custom values or formulas in if/else conditions?
Can I use custom values or formulas in if/else conditions?
Why does my date condition not match even though the dates look the same?
Why does my date condition not match even though the dates look the same?
Is there a limit to the number of conditions in a single if/else step?
Is there a limit to the number of conditions in a single if/else step?