Skip to main content

Troubleshooting If/Else Actions in Kyrios Workflows

This article explains how to diagnose and fix issues where If/Else actions in Kyrios workflows do not route contacts correctly due to condition logic, missing data, or misconfigured branches.

Updated over 3 months ago

Who This Is For / When to Use

This guide is for Kyrios users building workflows who notice contacts entering the wrong branch, skipping the Else path, or not triggering an If/Else action at all.

Use this article when:

  • Contacts do not enter the expected If or Else branch

  • Conditions appear correct but do not trigger

  • The Else branch never runs

  • The If/Else action cannot be added or shows errors


How the If/Else Action Works in Kyrios

The If/Else action evaluates contact data at the moment the workflow reaches the step and routes the contact based on whether the defined conditions are met.

If conditions are incomplete, conflicting, or reference missing data, contacts may route incorrectly or default to the Else path.


Why an If/Else Action Is Not Working as Expected

An If/Else action usually fails due to missing condition details, incorrect operators, or data that does not exist on the contact record.

How to Fix

  1. Open the workflow

  2. Click the If/Else action

  3. Review each condition segment

  4. Confirm the referenced field (tag, custom field, address, name) exists and contains data

  5. Save and re-test


Why Contacts Enter the Wrong Branch

Contacts enter the wrong branch when conditions overlap or contradict each other.

For example, using both “Is empty” and “Is not empty” for the same field within the same branch can cause unexpected routing.

How to Fix

  1. Open the If/Else action

  2. Review all segments in the If branch

  3. Ensure conditions are logically distinct

  4. Avoid conflicting AND/OR logic

  5. Test with multiple contact records


Why No Contacts Enter the Else Branch

If all contacts match the If conditions, the Else branch will never trigger.

This typically happens when the If condition is too broad or uses operators like Contains instead of Equals.

How to Fix

  1. Open the If/Else action

  2. Review the If branch conditions

  3. Tighten criteria (for example, use Does not contain or Is empty)

  4. Save and re-test with varied contact data


Why the If/Else Action Shows Validation Errors

Validation errors appear when required condition fields are not fully configured.

Examples include:

  • Operator not selected

  • Field not selected

  • Value missing

How to Fix

  1. Open the If/Else action

  2. Locate segments marked with warnings

  3. Complete all required dropdowns and values

  4. Save the workflow


How to Properly Test If/Else Logic Before Launching

Testing ensures contacts route correctly before the workflow is live.

How to Test

  1. Create or select test contacts

  2. Populate required fields (tags, names, addresses)

  3. Manually add contacts to the workflow

  4. Observe which branch each contact enters

  5. Adjust conditions as needed


How to Add an If/Else Action to a Workflow

The If/Else action is available in standard workflow builders.

Steps

  1. Open the workflow builder

  2. Click + Add Action

  3. Select If/Else

  4. Configure branches and conditions

If the action does not appear, refresh the page or create a new workflow.


Common Issues and Fixes

Issue: If/Else action does not appear

Fix: Refresh the builder or start from a supported workflow template.

Issue: Contacts skip the action entirely

Fix: Confirm the workflow trigger is firing and the contact reaches the step.

Issue: Conditions look correct but fail

Fix: Verify the contact record contains the expected data at runtime.

Did this answer your question?