Add Exit and Suppression Rules

Write every way out, and keep pause separate from stop.

See the situation

Start with the situation below. Next, we will work through an example together before you try the activity.

Samir · Workflow operator

The case

A reply, and four more scheduled touches

An exit ends one workflow, a pause suspends it, and a scoped suppression constrains later contact too.

Day 2: The person replies to the first email
Day 2 onward: The owner starts a live thread
Days 3, 6, 9, 12: Scheduled touches send anyway
Exit conditions defined: One: all steps completed
Final status: Completed successfully

Your task

Classify each event as completion, pause, suppression, or continue. Then check how the paused case resumes.

Need a little guidance?

You’re done when: The workflow stops for the right reason without erasing unrelated state.

Different exits have different reporting and re-entry consequences.

Need a reminder? Reopen the worked example

Watch one example first

A pause keeps work resumable. An exit ends this workflow. A person-level contact restriction can constrain later workflows too, so ending one workflow does not erase it.

Why this follows from the evidence

These controls have different scopes. Store the reason and scope instead of treating every non-running record as the same state.

GTM Lab

Saved locally

Workflow Specification · 0 of 8 sections started

Saved locally to your browser.

Case evidence

A reply, and four more scheduled touches

Day 2: The person replies to the first email
Day 2 onward: The owner starts a live thread
Days 3, 6, 9, 12: Scheduled touches send anyway
Exit conditions defined: One: all steps completed
Final status: Completed successfully

The record above finished with a status of completed successfully. Sort the conditions below into the three categories that behave differently.

Workflow workbench

Sort events by what they mean

Handle each event according to its scope. Then resume the paused case after the absence window and keep re-entry separate from suppression.

Person replies to the first email

Choose the resulting state

Automatic out-of-office reply

Choose the resulting state

Person asks not to be contacted

Choose the resulting state

Record is in a pending duplicate merge

Choose the resulting state

Conversation is booked

Choose the resulting state

The out-of-office window has passed. What happens to the paused cadence?

A new qualified event arrives after the prior instance finished. When can this policy allow re-entry?

Resulting state by eventFollow the example events in time order. No live integration runs here.

New event
Person replies to the first email
Choose what happens to this case.
Not checked
Temporary
Automatic out-of-office reply
Choose what happens to this case.
Not checked
New event
Person asks not to be contacted
Choose what happens to this case.
Not checked
New event
Record is in a pending duplicate merge
Choose what happens to this case.
Not checked
New event
Conversation is booked
Choose what happens to this case.
Not checked

Changes save in this browser as you work.

Inspect the example policy saved by this activity

These are the supplied example-plan entries, not another test. Complete the workbench above to save its result.

Which sorting is right?: In this model, an exit ends this workflow, a pause suspends it, and a suppression is stored on the person record for other workflows to honor under the stated policy.
Say why the pause has to stay distinct.: The operational view can look quiet in both cases, so store the reason and scope rather than inferring the meaning from inactivity.
Can someone this workflow has already finished with go through it again?: Names when, and names whether they resume or restart. It also matches the conditional exclusion Chapter 2 wrote, which is what keeps the two sections from contradicting each other.

Your place saves as you go.

Chapter 5 of 80 complete