What are the best practices for a journey, post completion in marketing cloud. In marketing cloud, once a journey is complete i.e. all communications have been delivered, tracking is available and contacts have exited the journey, journey status still shows running.

  1. Does such multiple journeys on same data extension impacts marketing cloud performance ? (Performance in terms of speed of execution and system load)
  2. Shall we manually stop each journey once it's complete ?
  3. Should there be an option which automatically stops journey once it's complete or should there be an option to specify (date time limit) which stops journey at specified date & time ?

2 Answers 2


1: You should be able to execute multiple journeys that reference the same data extension with relative ease, but once your data extension gets into the millions of rows it may impact performance, but it should not impact the entire system. I have noticed that numerous API calls to the same system objects can impact performance as well, so be careful if your journeys have "update contact" activities in them that are reaching out to large, shared data extensions.

2/3: There are only two ways to stop a journey currently: manually, and using the API.

  • Should we stop a journey manually once it's completed, in that case (big data and multiple journeys on same data extension) ?
    – ASHISH
    Nov 27, 2018 at 11:34
  • It depends on how you decided to begin the journey. If the journey runs when new data is added to a data extension then yes if it's complete it would be safe to stop to avoid any accidental entries. If it was a "run once" journey it's safe to keep running however, I'd recommend turning those off as well since it makes it easier for you to filter for "active journeys" in your journey folder view. Nov 27, 2018 at 14:13

You can also find best practices in the Help page.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .