An automation that is on sends by itself, to everyone who meets the trigger, without asking anyone again. That is why turning it on is separate from saving, with its own requirements β and pausing, editing and archiving affect the people already inside in ways worth knowing before you touch anything. The examples come from Casa Moura CafΓ©s' Welcome automation, fired by whoever joins the Store customers list.
The four statuses
- Draft β never turned on. Nothing is watched and nothing goes out.
- On β the trigger is being watched and the steps go out on their own. It cannot be edited.
- Paused β nothing goes out. People inside stay on the step they were at. It can be edited.
- Archived β ended for good. It cannot be turned on again.
Turning it on
Use Turn on in the editor's Activation panel, on the automation page or in the row menu. The button only appears after the first save and stays disabled while there are unsaved changes β turning on what is on screen rather than what is stored would be turning on something else.
The automation only turns on when:
- it has at least one email step, and every email step has a subject, a sender, content and the unsubscribe link ({{unsubscribe_url}}) in the body;
- what the trigger uses still exists β the list, segment, campaign, field or other automation may have been deleted since you saved;
- every condition uses fields that still exist and branches to a step that exists;
- the sending account is ready to send.
When something is missing, the refusal says what β for example, that step 2 is missing a subject, sender or content.
Who can turn it on
Turning on, pausing and archiving belong to whoever sends campaigns: Manager and Administrator. An automation that is on is a sending machine, and someone who cannot send a campaign cannot start one either. An Author builds, saves and deletes drafts, and asks someone on the team to turn it on. A Viewer can only look.
Pausing and editing with people inside
While it is on, the automation cannot be edited: the editor locks with a notice to pause first. This protects people waiting for a step from finding it changed. The path is Pause, edit, save and Turn on again.
When editing a paused automation, keep in mind:
- People inside keep their position, not the step. Someone stopped at step 3 continues from step 3 when you turn it back on, with the steps as they are now. If you remove or reorder steps, step 3 may be a different one.
- A wait in progress keeps its calculated time. Changing a wait from 2 to 5 days applies to whoever reaches it later, not to those already waiting.
- Whatever fell due during the pause goes out when you turn it back on. Anyone with a step scheduled during the pause gets it as soon as the automation resumes.
- With event triggers, the automation picks up where it stopped. Whoever joined the Store customers list during the pause also enters when Welcome is turned back on.
- With date triggers, paused days do not come back. The sweep only looks at today: anyone whose birthday fell while the automation was paused misses that year's greeting.
When it pauses itself
If an automation's sends are refused repeatedly β the sending account is no longer ready, the account's sending was suspended, a condition now uses a field that no longer exists β it pauses itself. The Paused automatically notice shows on the automation page and in the editor, with the reason. A single stumble does not pause anything. Fix the cause and turn it on again; people inside continue from where they stopped.
Archiving and deleting
- Archive stops the automation for good. Anyone waiting for a step leaves, with the reason automation archived. Its history and reports stay available.
- Delete only exists for Draft and Archived β one that is on or paused must be archived first. The automation and its run history go away, but the campaigns it already sent stay in the reports.
Monitoring: the automation page
Click the automation's name, or View runs in the row menu. At the top are three numbers: Enrolled (how many got in), Completed (reached the end) and Exited (left before the end). In the list, the Last sweep column shows when it last checked the trigger β for date triggers, the date evaluated.
Runs tab
Every time an email step goes out, a run is created: everyone who reached that step in the same sweep receives it together, in a campaign of its own, with When, Step, Enrolled and the sent, open and click counts. Click the campaign status to open its full report. These campaigns do not show up in the Campaigns list β this is the way to them.
Enrollments tab
Every contact who got in, with the status β Waiting, Completed, Exited or Failed β, the step they are on, Next step at and the Cycle. This is the screen to answer "did this customer get the second welcome email?". The filter at the top splits by status.
Why someone leaves before the end
Exit rules are checked when the next step falls due, not on entry β the wait between steps is what gives a person time to click, leave the list or unsubscribe. The reason shows next to the Exited status:
- unsubscribed, address bounced, marked as spam and address blocked β apply to every trigger: nobody in these situations gets automation email.
- left the list β with the Joined a list trigger, someone removed from the list before the next step.
- left the segment β with the daily trigger, when Exit when leaving the segment is on.
- the field changed value β with the custom field trigger, when the value is no longer the chosen one.
- clicked and opened β with the Opened but didn't click and Received but didn't open triggers.
- did not meet the condition β at an If step whose "those who don't match" is to leave.
- automation archived β was waiting when the automation was archived.
Where to go next
- Build an automation β triggers, steps and re-entry.
- Start from an automation template β ready automations to adjust.
- Campaigns β how to read the report each run produces.
- Segments β the audiences used by the daily trigger and the conditions.
In short: turn it on only after saving, with at least one complete email and the sending account ready; to edit, pause it, remembering that people inside keep their position and that paused days do not come back for date triggers; and monitor through the Runs and Enrollments tabs, where every early exit comes with its reason.