What is Stop Journey?
As the name suggests, Stop Journey terminates the execution of a journey from the point at which it is placed by the user. Stop Journey can be placed between the simple actions, conditioning actions, or looping actions as per the user's business requirement.
Benefits of using Stop Journey
A journey could have more than 100 actions in it. The more extensive the journey is, the more load it will cause on the server. Using Stop Journey to make the execution flow stop after a desired condition has been met, will help in reducing the load on the server thus reducing redundancies.
For a better understanding of the working of Stop Journey, here's a small use case illustrated.
You have a shop where you sell some products. Based on the subject of the emails you receive, you want to perform specific actions.
- If you get a Product Update email, you want to store the contents of the email in a Google Doc for future reference.
- If you get a Product Update email, you want to store it in a new row in a Google Sheet.
- If you get a Product Review email, you want to reply to the email.
To perform the desired action on the basis of the subject of the email, you can design your journey to have conditional checks in the following manner.
When you receive a new email via Gmail:
Check whether its subject contains the keywords Product Update.
If yes, then append the body of the email to a specified Google Doc and then stop the journey.
If the subject does not contain the keywords Product Update, the next steps of the Journey will come into play.
Check if the subject of the email contains the keywords Product Issue.
If yes, then add a new row to a specified Google Sheet and then stop the journey.
If the subject does not contain the keywords Product Issue, the next steps of the Journey will come into play.
Check if the subject of the email contains the keywords Product Review.
If yes, then send an email via Gmail to the reviewer.
In this way, you can create a journey with as many actions you like.
Please note that it is redundant to apply Stop Journey at the end of the last action because the journey automatically ends when the last action gets executed successfully.
Once the desired condition has been met, there is no need for the system to check for the rest of the conditions present in the Journey. Hence, the Stop Journey action ensures that the journey is stopped after the desired condition is met and its corresponding action is executed. This prevents the system from unnecessarily checking all the other conditions in the Journey.
Then, depending on your business requirement, include Stop Journey until where your journey should execute the actions.