Understanding the Limitation
The pause duration in Journey Builder is limited to 14 days, and this is a platform-level limitation. When a Journey is paused, the records in the Triggered Send queue will only be held for 14 days before they start falling off the queue.
The root cause of this limitation is the design of the Triggered Send queue, which is optimized for short-term pauses and is not intended for long-term storage of records.
Implications and Workarounds
While there is no direct way to extend the pause duration, teams running Journey Builder can design their Journeys to take into account this limitation. For example, they can use external data sources or custom activities to store records temporarily while the Journey is paused.
Alternatively, teams can consider using other Salesforce features, such as Automation Studio or Data Cloud, to manage their data and workflows, potentially bypassing the Journey Builder pause duration limitation.
Best Practices and Checklist
Designing Journeys with Pause Duration in Mind
- Plan Journeys to take into account the 14-day pause duration limitation
- Use external data sources or custom activities to store records temporarily
- Consider using Automation Studio or Data Cloud for workflow management
- Test and validate Journey designs to ensure they work within the pause duration limitation
- Monitor and adjust Journeys as needed to avoid record loss due to the pause duration limitation
Frequently Asked Questions
What is the maximum pause duration in Journey Builder?
The maximum pause duration in Journey Builder is 14 days.
Can I extend the pause duration using custom activities or external data sources?
While custom activities or external data sources can help manage records temporarily, they do not directly extend the pause duration limitation.
Are there any plans to increase the pause duration limitation in Journey Builder?
There are no announced plans to increase the pause duration limitation in Journey Builder.
What are the implications of the pause duration limitation for my Journey design?
The pause duration limitation requires careful planning and design of Journeys to ensure that records are not lost due to the limitation.
Need help shipping this in production?
Genetrix builds and untangles Salesforce Marketing Cloud and Agentforce setups for teams that want it done right the first time. If anything in this post sounds familiar, talk to us before it ships.
