Profiles exit journey prematurely in ÃÛ¶¹ÊÓƵ Journey Optimizer
In ÃÛ¶¹ÊÓƵ Journey Optimizer, profiles unexpectedly exit a journey without passing through a designated node. This issue occurs when the condition used to check the feedback status of sent messages is improperly configured, leading to inconsistent results. To fix this, review the condition logic, implement alternative logic, or consult with the implementation team.
Description description
Environment
ÃÛ¶¹ÊÓƵ Journey Optimizer (AJO)
Issue/Symptoms
- Profiles exit the journey prematurely.
- The condition checks the feedback status at the zeroth position in an events array, which does not always contain the relevant event due to multiple simultaneous events.
Resolution resolution
To resolve this issue, follow these steps:
- Review the condition logic and avoid using conditions that rely on checking the feedback status at a fixed position (e.g., zeroth node) in an events array. Recognize that multiple events can occur simultaneously, and the desired event might not be at the expected position.
- Implement alternative logic by using collection functions to dynamically identify and evaluate the correct event within your dataset. For example, use expressions such as
<listExpression>.last(<condition>)to fetch and evaluate the last relevant event based on specific criteria. - Consult with your implementation team to develop an alternative approach tailored to your specific use case. Ensure that any new logic accounts for potential variations in event order or timing.
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f