Brief Overview

Split and error handling steps evaluate the state of the application and determine the next step in a Smart Walk-Thru flow. If these steps are failing to trigger or taking the wrong path, the cause is typically a timing issue, an incorrect rule configuration, or an element inside an iframe.

Troubleshooting Steps

Check for page load timing

If the step triggers before the application finishes loading, WalkMe may not find the element or condition it needs.

• Add a Wait for step immediately before the split or error handling step
• Set the condition to pause the flow until a specific element confirms the page is ready, or add a 1-2 second delay for slower network speeds

Wait For Steps: Getting Started Guide

Review rule configuration

• Verify that And / Or operators between multiple statements are grouped correctly
• Confirm that jQuery syntax is valid if using technical selectors
• If an element is not being consistently identified, check the element's selector stability in the Condition Builder before adjusting precision

Address elements in iFrames

If the element being evaluated is inside a cross-domain iframe, WalkMe requires an additional step to access it.

• Add a Switch to Frame step before the split or error handling step
• Confirm the element is correctly identified within the iFrame boundaries

Switch to Frame Flow Steps

Use the Flow Tracker for debugging

• Open the Flow Tracker and run the Smart Walk-Thru to the point of failure
• Review the specific error message for the split or error handling step to identify the root cause

Flow Tracker

Best Practices

• Use stable, unique elements for split and error handling step conditions to avoid false positives — avoid elements that load dynamically or change between page states
• Test split logic across multiple scenarios before publishing, including edge cases where the expected element may not appear
• Keep the number of conditions per split step to a minimum to reduce evaluation time during the flow