Timing plays a critical role in how your workflows behave. Understanding how Wait action work, especially in relation to conditions, helps you control when actions happen and which customers receive them.
Conditions split customers into two branches: True and False. A key thing to understand is that conditions are evaluated at a specific point in time (point-in-time evaluation).
Suppose you have a condition:
Order count = 0 (over all time)
True → Customer has never purchased
False → Customer has purchased before
While a customer is in the workflow, they can place an order at any time. So the moment when the condition is evaluated determines which branch they enter.
If you add a Wait action before a condition, customers will wait until the delay is over before the condition is checked.
If you plan to send emails in both the True and False branches, we generally recommend:
✅ Send the email immediately after the condition
❌ Do not add a Wait action right after the condition
Why?
Once a condition is evaluated, the customer is assigned to a branch based on their status at that moment.
If you add a Wait action after the condition, the customer’s data may change during the wait period, meaning they might no longer meet the criteria of the branch they are in.
Sending the message immediately ensures:
The message matches the customer’s current status
The workflow logic remains accurate and predictable
_RK9EwjoK.jpg)