# Follow and edit an active scenario

> You run an active scenario from its diagram: how many contacts enter it, where they stop, who is in progress. You can edit it without disturbing the contacts already on their way.

## Steps

1. Open **Automation › Scenarios** and click the scenario. On a computer, **Statistics** is already turned on: each block shows its contacts entered or its messages sent, and each branch its share, for example “OK · 81 %”.
2. Choose the period at the top: **7 days**, **30 days** or **Since activation**.

3. The **Contacts** panel on the right sums up: **Entered**, **Running**, **Finished**, **Handed to the team**, **Stopped**. The **Stop reasons** say why: **A team member wrote**, **STOP**, **Window closed without approved message**, **Stopped by hand**, **Sending error**.
4. Under **Running**, each contact shows their step. Click **Stop** to take them out of the scenario.

5. To edit, click a block and change its setting. Your changes are saved on their own in a draft: the label **Unpublished changes** appears, and the live version keeps running.
6. Click **Publish changes** and confirm. Contacts already in progress finish on the old version; new ones follow the new version.

7. In **More actions** (⋯), **Version history** lists each published version: **Go back to this version** puts it back in the draft, ready to publish.
8. **Pause**, in the same menu, stops new entries. Choose what happens to the contacts in progress: **Freeze them: they continue on resume**, or **Stop them**. **Resume** restarts the scenario.

## When a scenario stops on an error

- The conversation thread shows “The “…” scenario stopped on an error: reply to the customer yourself”. The WYP.chat team is alerted at the same time.
- A scenario message refused by WhatsApp after sending leaves the line “Message from the “…” scenario not delivered” and the team is notified.
- If the person who created or changed the scenario has left the workspace, its messages are sent in the name of the workspace owner. The owner and administrators get a notification, once per scenario, and the change is recorded in the log.

**Good to know** A supervisor prepares the scenario and clicks **Request activation**, with an optional message: the administrators receive the request and a banner offers them **Activate** or **Decline**. On an active scenario, only an administrator publishes changes. A supervisor sees an active scenario created by another member as read only. In a conversation, the contact record shows the **Running scenario**: **View** opens the diagram, **Stop** takes the contact out of the scenario. At the top of the thread, the “who is replying” badge also shows the running scenario and what it is waiting for: **Take over** stops it, **Let it run** lets it carry on. When your AI agent starts a scenario or works in an **Ask the agent** step, the thread says so in one line: “Coucou started Appointment booking”, “Coucou understood: “Thursday””, or an **Agent draft** card to send.

## Related articles

- [Create a scenario](https://wyp.chat/en/help/creer-workflow) Create a WYP.chat scenario from the gallery or from scratch, started by a message or by your AI agent, test it in the simulator, then activate it.
- [Send an interactive message (buttons, list, carousel, products)](https://wyp.chat/en/help/boutons-listes) An interactive message lets the customer reply with a single tap: a button, a list row, a carousel card.
- [See who is replying to the customer](https://wyp.chat/en/help/qui-repond) The “who is replying” badge in Messages shows who holds the conversation: your team, a scenario, your AI agent or another tool, and how to take over.
- [Your AI agent on WhatsApp, Messenger, Instagram, Telegram](https://wyp.chat/en/help/agent-ia-messageries) Your AI agent answers your customers on WhatsApp, Messenger, Instagram and Telegram once the owner has turned it on and you have chosen, channel by…

**Learn more**

- [Automate WhatsApp Business with scenarios](https://wyp.chat/en/features/workflows)

---

Source: https://wyp.chat/en/help/suivre-workflow · Updated on 12 October 2026