Enrollment History & Execution Logs

Last updated: April 12, 2026

Last Updated: April 12, 2026

Customer-Facing Guide

What this page is for

Enrollment History & Execution Logs are the fastest way to confirm whether a workflow actually enrolled a contact, which steps ran, where the workflow paused, and which step most likely explains the outcome you are seeing.

Questions it helps answer

  • Did the contact enroll at all?

  • Which step definitely ran last?

  • Did the workflow pause at a delay or wait step?

  • Did a condition, branch, or missing prerequisite stop the workflow from continuing?

When you should check logs first

  • A customer says the workflow never started.

  • A step was skipped or ran in the wrong order.

  • A message appears to have been created but not sent when expected.

  • You need to separate “bad workflow logic” from “good workflow logic with bad timing.”

A simple troubleshooting sequence

  1. Confirm whether the contact enrolled.

  2. Identify the last step that definitely ran.

  3. Check whether the workflow hit a delay, wait, or branch that explains the current state.

  4. If the workflow reached the send step, continue troubleshooting message creation/delivery rather than enrollment.

  5. If the workflow never reached the send step, fix the earlier branch, condition, data dependency, or timing issue first.

What common outcomes usually mean

  • No enrollment found usually means the trigger or entry criteria did not match the way the contact actually entered the system.

  • Enrollment found but later step missing usually points to a branch, condition, delay, or missing prerequisite.

  • Workflow reached the message step but the message outcome is wrong usually means the trigger was fine and the next investigation belongs in delivery, line health, or message-state troubleshooting.

Why this matters

Many workflow problems look identical from the outside. Execution logs let you separate “never enrolled,” “enrolled but paused,” and “enrolled and reached the send step.” That saves time and keeps you from fixing the wrong layer.

Best practice

Use logs together with the contact timeline and any related workflow docs. If you see a timing-sensitive step like Assign To User, tags, or custom variables, check whether a short delay would make the workflow more reliable.

Related guides