> ## Documentation Index
> Fetch the complete documentation index at: https://docs.growthxai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Editing a Live Sequence

> Change queued message text, reschedule waiting leads, edit one lead's next action, and move leads when the sender pool changes.

Once leads are moving, changes have to reach two places: the steps themselves, and the work that is **already queued** for the next day or two. The builder handles both, and always tells you the count before it acts.

## Text that is already queued

Edit a message step on a live sequence and the config panel says:

> 12 messages already queued with the old text.

Open the list to see each lead, its send time and its text. When you [publish](/sequences/creating-managing-sequences/draft-and-publish), you choose **Update them too** or **Leave as they are**.

The same happens for timing. Change a delay and you are offered **reschedule 40 waiting leads**.

## One lead at a time

The lead page has a **Queued actions** card listing what is planned for that lead next. Each row gives you:

* **View / edit** — the template as stored, and the preview for this lead. Edit the text and it is sent exactly as written, with no further variable filling.
* **Send at** — move the action to a different time.
* **Skip this step** — cancel just this action; the lead carries on to the next step.

<Note>
  Steps are planned a day or two ahead, so a lead with nothing queued is normal. To end the sequence for the lead, exit the enrollment instead of skipping each step.
</Note>

A voice-note step shows "the sender's recorded clip is used" rather than text. A step whose text has not been rendered yet says so: it is filled in from the live step when it sends.

## Changing the sender pool

Adding a sender to a running sequence only affects leads enrolled afterwards — unless you move the existing ones, which the builder offers to do for you.

Change the **Pool** and you get:

> Move 140 waiting leads to the new sender?

Only leads that have **had no outbound action yet** on their current sender are eligible. Nothing is sent twice and no lead ever sees two senders on the same thread. The dialog counts the rest so you know where they went:

| Group                 | What happens                                                                                  |
| --------------------- | --------------------------------------------------------------------------------------------- |
| **Nothing sent yet**  | Can move. Their queued actions are planned again for the new sender, inside its daily limits. |
| **Already contacted** | Stay with their current sender                                                                |
| **Not connected**     | Counted separately so you can see the shape of the pool                                       |

Removing a sender offers the same choice for its untouched leads: move them, or leave them. Leads it has already contacted stay with it, or exit — with the counts shown for each choice.

<Warning>
  An active sequence needs at least one sender. Emptying the pool is refused.
</Warning>

## Deleting a step leads are on

You're asked what to do with them, folded into the publish dialog:

* **Skip in-flight** cancels that step's queued actions and moves the leads to the next step.
* **Cancel in-flight** ends those enrollments with the reason *node deleted*.
* **Keep step** cancels the delete.

The choice is recorded in the audit log.

## Related articles

* [Drafts, Publishing and Version Pinning](/sequences/creating-managing-sequences/draft-and-publish)
* [Rotate Sender Explained](/sequences/creating-managing-sequences/rotate-sender-explained)
* [Recover Failed Leads](/sequences/sequence-troubleshooting/recover-failed-leads)