Add 'Pause' Functionality for Journeys

[#1]

Description:
Introduce a "Pause" functionality for journeys, allowing temporary halts without permanently stopping them. This would help address short-term issues while preserving the integrity of the journey data.

Why is this feature important to you:
A "Pause" feature provides flexibility in managing journeys by enabling quick fixes without disrupting the entire process. It ensures that IDs remain consistent and avoids mixing or fragmenting reports, which is essential for accurate performance analysis.

How would you like the feature to work:
The system should include a "Pause" button alongside the existing "Run," "Stop," and "Close" options. When paused, the journey should retain its current state and resume seamlessly once issues are resolved, with all IDs and reporting data remaining intact.

Current Behaviour:
Currently, the only available options are to run, close, or stop a journey. Stopping a journey disrupts continuity, alters IDs, and complicates reporting, making it difficult to manage temporary interruptions effectively.

[#2]

Hey! We've had a lot of success for the functionality you're describing by making new versions! It keeps the continutity for the OOTB IDs. You can additionally combine this with a 'Close to new entrants' on the previous itteration and it should be able to solve for those issues you're describing

[#3]

Hi @TylerKrause ,

Thank you for your comment!

To clarify, the functionality we are looking for is the ability to pause all steps within a journey—not just the entrance of new profiles.

We already have mechanisms in place to manage the flow of new profiles into journeys.

However, our use case requires the capability to pause the entire journey's progression, effectively halting all steps until we choose to resume it.

This would allow for more comprehensive control during updates or troubleshooting, ensuring a seamless experience for profiles already in the journey.