Who is in an automation

“Why did this person get that email?” is the question support actually gets asked. The journey view answers it by showing one contact’s entire path through an automation.

Finding it

From any automation, follow See who is in this automation, and where they are. That lists everyone enrolled, most recently enrolled first, with what each of them is currently waiting on. Click anyone to open their journey.

What a journey shows

• Every step they have been through, in order, with the time they reached it.
• Which branch they took at each fork.
• When each email was opened or clicked, and whether delivery failed.
• Where they are standing right now, marked “here now”.
• The steps still ahead of them, dimmed — the path ahead is as much of the answer as the path behind.

Editing an automation people are already inside

You can edit a running automation. If you delete a step somebody is currently waiting at, they are moved on to the step that follows it rather than being stranded, and the editor tells you how many contacts were moved. If there is no following step, they finish the automation.

This is also why the flow view is the only editor for a branched automation: the simple step list cannot describe two paths, so it refuses to save changes to one rather than quietly flattening it and stranding everybody on the discarded side.