> For the complete documentation index, see [llms.txt](https://help.getmobly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.getmobly.com/help-center/pulse/how-to-pause-or-cancel-a-sequence.md).

# Pausing, editing, or canceling a sequence

You sent a sequence and something's off — wrong template, wrong list, wrong cadence. Or worse, you're watching a lead get the same email three times in a row. Here's how to take control.

## Quick reference

| What you want to do                                | What to do                                                       |
| -------------------------------------------------- | ---------------------------------------------------------------- |
| Stop the whole sequence from sending anything more | **Pause** the sequence (toggle it from Active to Paused)         |
| Stop sending to one specific lead                  | **Cancel** that lead's enrollment from the sequence details page |
| Tweak the template or timing for future sends      | Edit the sequence (pause first, edit, resume)                    |
| Permanently remove the sequence                    | **Delete** the sequence                                          |
| Re-send to leads who were canceled or completed    | Use **Re-enroll** from the sequence details page                 |

## Pause a sequence

Pausing is the safest "stop everything" button. Pause when you're not sure exactly what's wrong but you want sends to halt while you investigate.

1. Go to **Pulse → Sequences** in the Hub.
2. Find your sequence in the list. Click the Active/Paused toggle to flip it to Paused.

When a sequence is paused:

* **No new leads enroll**, even if they match the trigger.
* **Already-enrolled leads stop progressing.** Their pending steps are held — not sent, not skipped, not lost.
* **Already-sent emails stay sent.** Pausing can't recall something that's already gone out.

When you resume, pending steps pick up from where they left off. If a step's scheduled date passed during the pause, the step skips forward to the next valid time (or honors its end-date setting, if one is configured).

> **If you need to stop sends right now and aren't sure what else is happening:** pause first, diagnose second. You can always resume.

## Cancel one lead's enrollment

If only one lead (or a small group) is affected — wrong person enrolled, lead asked to be removed, etc. — cancel that enrollment without pausing the whole sequence.

1. Open the sequence in **Pulse → Sequences**.
2. Go to the **Enrollments** view.
3. Find the lead. Use the row action to **Cancel** their enrollment.

The enrollment status flips to CANCELLED. No more sends go to that lead from this sequence. The lead can be re-enrolled later if needed.

## Edit a live sequence

You can edit a sequence while it's active, but it's safer to pause first if the change is non-trivial.

**Safe edits without pausing:**

* Renaming the sequence
* Editing copy on a step that hasn't been scheduled yet (no leads at that step)

**Edits that benefit from pausing first:**

* Changing the timing on a step
* Reordering or deleting steps
* Adding new steps
* Changing the trigger

When you change a step's content, **only sends that haven't been queued yet pick up the new content.** Anything already sent stays sent. Anything that was already scheduled to send within the next few minutes may have been queued with the old content — pause first if you need certainty.

After editing, resume the sequence.

## Delete a sequence

Deleting removes the sequence permanently. Anything that hasn't sent yet won't send. Existing enrollment records remain for audit but no further activity happens against the sequence.

> **Prefer pausing to deleting** unless you're certain you won't want to resume. Pausing keeps your edit history and lets you reactivate the same sequence later. Deletion is irreversible.

## Emergency: a sequence is sending too many emails

If you're seeing a lead receive the same email multiple times, or sends going out faster than configured:

1. **Pause the sequence immediately** — first action, before investigating.
2. Open the **Enrollments** view to see who got what. Cancel the worst-affected enrollments.
3. Check the **Triggers** — multiple overlapping triggers shouldn't cause duplicate sends (Mobly deduplicates enrollments), but a misconfigured Tag trigger could be re-enrolling leads each time a tag is reapplied.
4. Contact your CSM with the sequence name, the affected lead(s), and what you observed. Mobly's team can audit the send history server-side and confirm what actually went out.

## Re-enroll leads

You may want to send a sequence to leads who already completed it, were canceled, or were marked ineligible — for example, after editing the sequence content.

1. From the sequence details page, use the **Re-enroll** action.
2. Optionally scope it to a specific list of leads, or re-enroll everyone who isn't currently active.

Re-enrolled leads start the sequence from step 1.

## Related articles

* [Understanding Sequences](/help-center/pulse/understanding-sequences.md)
* [Setting Up a Pulse Sequence](/help-center/pulse/setting-up-a-pulse-sequence.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.getmobly.com/help-center/pulse/how-to-pause-or-cancel-a-sequence.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.