Documentation

Manual mode

Suggest Edits

Manual mode is a powerful capability to allow you to manually run a full or parts of a journey at any given time. It's in contrast to running a journey one-time, always or on a specific schedule.

It specifically allow you to run:

  • A specific node in a journey
  • A journey up-to a specific node

How it works

When you set up a journey, you must make sure you set its Journey Schedule to Manual. This makes sure the journey is ready to manually be run after it's Saved & Published.

After you have published the journey, your nodes will have 2 new options next them.

  • Run until this node
  • Run this node only

Run until this node

This will start the journey and execute every node up-to & including the selected node. It will then stop running any consequent nodes. Keep in mind this will only run any journey paths which somehow can lead to this node and not otherwise.


Run this node only

This option will only run customers that are at this node.


These two options are available for the following node types:

  1. Entry node
  2. Criteria node
  3. Experiment node
  4. Destination node

Let's walk through an example that combines the 2 options above

  1. Imagine you have this simple journey, where you check your customers to see if any of them has phone number 4444444.

  2. You decide to run the journey until the success destination node on the bottom left, after you've saved and published the journey.

    1. Notice that all the numbers are 0 in both the pending (yellow) and processed (green) boxes.
  1. You will see the journey is processing and after a minute or two you can refresh the page to see the nodes updated.

  1. You can see that our journey has run and

    1. One user has landed on the success destination node and was also processed, which means they were exported to the destination.
    2. No users were sent to the Failure destination node (bottom-right). This is because the journey processor only looks at the leading path to the node we ran the journey up to (ie, success destination node).

  2. Now we're going to run the journey differently. We will run it up to the criteria node only, to see how this changes the customer distribution.

    1. Please note that in our journey settings, we have allowed for users to re-enter the journey at every run -- this is recommended for when your journey schedule is set to manual mode.

    2. This also re-runs the entire journey as if it was the first time we were running it

    3. Let's run the journey until the criteria node

  3. Now you can see that both destination nodes have users in their pending (yellow) box.

    1. This is because the journey runs and processes the criteria node and pushes the users to their respective nodes and stops.

      1. you can now run each node separately to have your respective users be exported to their respective destinations.


Edit a journey after it's published

One of the key values of manual mode, is that you can edit your journey after it's published. If you realize you didn't set up your criteria node correctly, you can update it and run the journey up to that node again.

Keep in mind that you can run a journey in manual mode until you feel confident about your setup, before changing the settings to a different schedule.

You can only switch the schedule from manual mode to any other schedule and never to manual mode from another schedule.

Once you change the settings and save the journey, you'll have to confirm the following changes before they take effect.


Some use cases

  1. Imagine you have a criteria node and want to see how many of your users meet or don't meet the criteria, when they reach that node. Use the "Run until this node" option on the criteria node at hand.
  2. Imagine you have an experiment node and want to know how your customers get distributed after the run through that node. Use the "Run until this node" option on the experiment node.
  3. Imagine you want to slowly walk through each node in the journey. Use the "Run this node only" as you traverse through the journey, to see the impact of each node.
  4. Rerun the same journey -- This is helpful to modify your journey and re-run a flow up to a certain node until you reach your desired behavior

Updated 1 day ago