A Wait For Condition will make the Smart Walk-Thru wait for a certain amount of time or until a certain condition is met before continuing to the next step.
Watch the video to learn about Wait For Condition.
Key Takeaways |
---|
A Wait For Condition has several uses. Use it to wait for:
The Wait For Condition can be configured to wait for a specific time duration or use the Condition Builder to determine when to continue playing your Smart Walk-Thrus. |

Waiting with Wait For Conditions
A Wait For Condition can be added anywhere in a Smart Walk-Thru. When WalkMe gets to the Wait For Condition, the Smart Walk-Thru will wait to play the next step until a certain number of seconds have passed or the associated rule(s) is/are True.
The figure shows a Wait For Condition in the WalkMe Editor.

Why Delay Flows Intentionally?
Wait For Conditions can be necessary for making the user experience feel more smooth and to make sure Smart Walk-Thru steps play at the correct pace.
While it won't be part of our initial build, a Wait For is usually added as a troubleshooting tactic when we notice something not functioning ideally.
For example, we don't want our Smart Walk-Thru steps to preemptively play when the user hasn't even reached the next step yet! It's is also commonly used when the page loads too fast, and WalkMe doesn't have the time to detect the element which might cause the Smart Walk-Thru to stop.
The figure shows how the Enter Quantity step is playing too quickly, causing it to cover drop-down selection.

Next, we'll go through a scenario on our Eddie's Depot platform. In this scenario, our previously built Split Step is evaluating too fast, causing our guidance in the Yes branch to not play correctly. Because of this, our Split Step, which was created to reduce user confusion, is now causing more confusion because it isn't evaluating properly.
To resolve this confusion, we'll add a Wait For Condition to our Smart Walk-Thru to pause WalkMe so that it may evaluate our Split Step more accurately.