Enrollments & Runs

Every automation page has two history tabs — Runs and Enrollments. They answer different questions, and most confusion about automations comes from mixing them up.

Understanding runs

A run is the record of one trigger firing. Every time the trigger event happens and the automation evaluates it, one run row is created. The run shows whether the conditions matched and what the steps did.

If every step can happen immediately, the whole workflow finishes inside that single run. Nothing else is created. A one-step automation like "donation submitted → add contact to audience" only ever produces runs.

The Runs tab answers: how many times did this fire, and what happened each time?

Understanding enrollments

An enrollment is one contact's place inside an automation that spans time. Think of it as a bookmark: it records which step the contact is parked at and when the next step is due.

An enrollment is created in exactly two situations:

1. Something must happen later. A run executes steps instantly, top to bottom. The moment it reaches a Wait step, or finishes a step whose delay has more steps after it, the rest can't happen now — the contact is parked with an enrollment and picked up when the delay elapses. A delay after the final step parks nothing, because there is nothing left to run.
2. The contact entered through a list-based door. Manual enrollment, audience triggers, segment triggers, and scheduled triggers all place contacts into the workflow directly. These always create an enrollment, even when the steps run immediately.

The Enrollments tab answers: who is inside this workflow right now, and who has been through it?

Instant automations

An event-triggered automation with no delays never shows anything on the Enrollments tab. That's normal — check the Runs tab for its history.

Enrollment sources

The Source column shows how each contact entered:

• trigger — handed off from a run when the workflow hit a delay
• manual — an admin used the Enroll Contacts button
• audience — an audience subscribe/unsubscribe trigger
• segment_trigger — the contact entered the bound segment (each contact enrolls once, the first time they match)
• scheduled — a scheduled run enrolled matching contacts (contacts who finished can re-enroll on later runs)

Enrollment statuses

• Active — parked at a step, waiting for its next run time.
• Completed — walked through every step to the end.
• Cancelled — exited early. This happens when the contact hit an exit goal, unsubscribed, the automation was deactivated, or an admin cancelled them.
• Failed — a step errored and the workflow stopped for this contact.

Cancelling a contact

Use the ban icon on an active enrollment to pull one contact out of the workflow. Steps that already ran stay in history; remaining steps are skipped. Completed and cancelled enrollments can't be cancelled again — the icon explains when it's unavailable.

Enrolling contacts by hand

The Enroll contacts button on the Enrollments tab opens a picker for adding contacts directly. Contacts already actively enrolled are skipped, so you can't double-enroll someone mid-flow. Manual enrollment is available on active, user-created automations.