Your Send list keeps its sections and its connections
In Auto Flows, renaming, reordering or deleting an option on a Send list or Send buttons step no longer disconnects the branches wired to the others — and a Send list now reaches your customer grouped under the section titles you wrote.
Released 23 September 2026
Tidying up the options on a list or buttons step could quietly break the flow behind it. Now every option keeps its branch whatever you do to the others, and a Send list arrives grouped the way you wrote it.
What's new
- Rename, reorder or delete options freely. Each option on a Send list or Send buttons step now keeps its own branch from the moment you add it, whatever you later call it and wherever you move it. Before, renaming an option could leave its connection hanging off a branch that no longer existed — out of sight on the canvas, impossible to delete, and stopping you activating the flow, or publishing your changes, with an error nothing on screen could fix. You did not even have to rename anything: a brand-new Send list, wired up and saved as it was, could end up the same way.
- Deleting an option takes its connection with it, instead of leaving it behind out of sight. The options that remain stay connected.
- Messages already sent still work. A customer who taps an option on a list or buttons message sent before your edit still lands on the right branch.
- Your sections reach your customer. A Send list written in sections used to be flattened into one long list when you saved it. Your customer now sees the rows grouped under the section titles you wrote, and the step's card in the builder shows the titles too. Sections only group the rows — every option still has its own branch — and a list without section titles is sent exactly as before.
- Every section needs a title once there is more than one. That is WhatsApp's rule, so the builder now asks for the missing title before it saves, rather than the list being turned away later. Lists you send from a chat get the same check before they go.
If a flow was already caught by this
Open it and the builder clears the stranded connections for you, with a note saying how many it removed — for example, "Removed 1 connection from a list or button option that no longer exists — reconnect it." Wire those branches up again, then activate the flow or publish your changes as normal.
The builder does not guess where a removed connection was meant to go. Sending a customer's choice down the wrong branch would be worse than asking you to reconnect it, so that step is left to you.