21 October 2026
A customer who sends several messages before the bot's first reply no longer gets the opening sequence of a Chat Flow twice; the burst starts one run, and a run that was replaced stops sending at its next step.
One run per customer, even when the first messages come in a burst
Fixed. When a customer sent two or three messages within a few seconds before the bot answered ("hi", "good evening", "where are you?"), each message arrived as its own request and each could start the flow. The second run replaced the first, but the first had already begun its opening sequence and kept sending it, so the customer saw every opening message twice, sometimes three times. Now the first message of a burst is the only trigger, and a run that has been replaced or cancelled stops at its next step instead of finishing its sequence. When a flow starts.
Changelog
New endpoints, improvements and breaking changes to the WhatsApp Platform API — newest first.
20 October 2026
Chat Flows "If no reply" gains an optional closing message the customer receives when a run is closed for inactivity; the inactivity reminder no longer counts as a message from your team, so a customer who answers late starts a fresh run; on Business API numbers a free-text send outside the 24-hour window no longer vanishes — the composer locks and says why; a lead flow no longer creates a second lead next to an open lead that holds the number without a CRM contact; edits or deletions inside a WhatsApp group stay in the group chat instead of opening a one-to-one chat and a lead; and videos or documents sent from Bitrix24 on a QR number no longer fail at 15 seconds while the file still reaches the customer.