You are here:
Journey Builder Configuration Recommendations
As part of journey validation functionality, Journey Builder makes recommendations about configurations that can impact system performance. These recommendations don’t prevent you from activating your journey.
| Recommendation | Description |
|---|---|
| Approaching Salesforce Data Entry Limit | You're near the limit of active journeys with a specified entry source. To free up bandwidth, delete the entry source or stop unnecessary running journeys. |
| Back-to-Back Decision Splits | Delete a decision split or add an activity between the splits. |
| Connect a Journey to a Campaign | To use the advanced capabilities of a journey, connect the journey to a campaign. |
| Custom Activity Timeout Too Long | Set the timeout limit to 10,000 milliseconds or less. |
| Decision Split | Use an ETL tool such as Automation Studio for large-scale segmentation before admitting contacts into Journey Builder instead of filtering contacts within the entry source. |
| Final Wait Activity Exceeds 3 Minutes | Reduce the final wait activity to 3 minutes or less or remove it if it's not needed. |
| First Activity is a Decision Split | Consider doing additional audience segmentation before entering the journey. You can also use an entry filter instead of starting the journey with a decision split. |
| Improve Performance with High-Throughput Sending | To improve the performance of journeys with email activities, turn on high-throughput sending. |
| Journey with no Messaging Activities | Use Flow Builder for non-messaging use cases, such as CRM updates or segmentation. |
| Message Priority | To ensure timely delivery for inbound messages, set this journey’s priority to High. |
| Refresh Email Content | This content was last modified more than 6 months ago. To refresh the content, use Einstein to generate the body copy or subject line. You can also use Journey Builder Path Optimizer to determine if the content is still relevant. You can update content in a running journey without creating a new journey version. |
| Reused Event Definition | This event definition is used in 10 or more journeys. To improve journey performance, create another event definition. |
| Too Many Activities | Limit your journey to 150–200 activities. Consider breaking your journey into multiple smaller journeys or reducing unnecessary waits and decision splits. |
| Update Journey Type | To trigger the send of one transactional message, create a transactional journey or a transactional API request. |
| Use Flow to Modify CRM Objects | Use Flow Builder for CRM activities such as Account, Lead, or Opportunity. |
| Wait By Duration as the First Step of Journey | Consider removing the Wait activity at the beginning of your journey and using the Entry Schedule instead. |
| Wait By Duration in the Middle of a Journey | Remove any Wait activities in the middle of your journey that are less than 15 minutes. |
| Wait By Duration with Engagement Split | To give subscribers time to engage with your journey, allow at least 1 hour between the message activity and the engagement split. |
| Wait Duration Greater than Six Months | Reduce the wait duration to less than 6 months, or exit the members and create a new journey for them. |
Did this article solve your issue?
Let us know so we can improve!
