Member Execution

A member records a lead’s enrollment in a program. It preserves when the lead entered, the current step and when the next action is due. The last action time helps Marketing Operations locate recent work. The execution-history total includes waits and errors, so inspect each outcome before treating an action as successful. A program can be Active while a particular member is Paused, Exited or Completed.

The member’s execution history explains each action. It links the enrollment to the step and records the time, outcome and relevant detail, including the branch result or error message. When a lead appears stuck, start with that history and compare it with the current cursor. A due date identifies work to inspect; it does not by itself explain whether an earlier action succeeded.

• Enrollment. The profile feed is checked against every audience condition for an Active program. A matching lead starts at the first ordered step, subject to the concurrency limit and global suppression. At the limit, the enrollment is Queued for operating review.
• Due execution. The execution workflow scans Active members with due work every five minutes. It advances each member through a program step and records the action’s outcome. A wait schedules later work; a branch follows its configured destination. Email and webhook actions require their connected service results to be checked.
• Exception investigation. Follow an error to the affected enrollment and step before correcting the cursor. Read the explanation and compare the intended action with its recorded result. Inspect Paused members separately and agree the correction before resuming work.

Decide who reviews Members Due and who may correct an enrollment. Give the troubleshooting team the history access needed to inspect the affected action. Rehearse a wait, both branch paths and a goal check against the same lead. Confirm the timestamp interpretation so the daily work list and the scheduler’s due-time scan can be understood together.

Agree how the email-send service, CRM field updates and webhook destinations return results. Keep the receiving system’s reference available during an investigation. Before resuming an interrupted journey, check what has already happened at the destination and whether repeating the action would repeat the business effect. Marketing Operations and the program owner should agree the next step from that evidence.

Enroll a test lead in a short journey with a wait followed by a branch. Inspect the current step and next-run time before and after execution. Follow the history to confirm which branch was taken and that its destination belongs to the intended program. Run an email action and compare the rendered message with the service result and history entry.

Separately rehearse the final step with no remaining next-run time, no achieved goal and no matching exit rule. That enrollment should become Completed. Compare it with a member that becomes Exited after achieving the goal. Have the operator explain both results without treating the end of a sequence as proof of a successful marketing outcome.

• Members Due — Active enrollments with work due by today.
• Members On Hold — Paused enrollments with their current steps and timing.
• Member Execution Errors — Failed actions with the affected member, step and error explanation.

Rehearse enrollment and execution and review exits and completion.