Cancelling Flow Starts: Stopping Queued Messages During Large Sends

When you start a flow or broadcast to many contacts, messages are queued and delivered gradually based on your channel’s sending rate. The Starts log (Flows tab) and the Broadcasts tab let you monitor sending progress and cancel a send in progress. Cancelling stops delivery only for contacts still waiting in the queue—contacts who already started the flow or received the broadcast are not affected.

Quick setup checklist

Monitor large sends and cancel queued flow starts or broadcasts when needed.

  1. Understand why flow starts and broadcasts take time
  2. Monitor active flow starts and read the progress bar
  3. Cancel a flow start that is still sending
  4. Monitor and cancel a broadcast that is still sending
  5. Know what happens after cancellation and key limits
1
Understand why flow starts and broadcasts take time

When you start a flow or send a broadcast to many contacts, messages are not delivered all at once.

  • Channels send messages at a limited rate
  • Messages are queued and processed over time
  • Some contacts may receive messages later than others

Note: This behavior is expected and depends on your channel provider’s sending limits.

2
Monitor active flow starts and read the progress bar

Use the Starts list to monitor flow starts that are still sending.

  • Navigate to the Flows tab
  • Click Starts in the left-hand sidebar

[CAPTURE: Show the Flows page with Starts selected in the sidebar.]

For flows that are still sending:

  • A progress bar appears below the flow name
  • The total number of contacts being started is displayed
  • You can see how many contacts are still waiting to receive the flow

[CAPTURE: Show a flow start entry with an active progress bar and contact count.]

3
Cancel a flow start that is still sending

If you need to stop a flow start while it is still sending:

  1. Locate the flow in the Starts list
  2. Click the X icon at the end of the progress bar

The flow start is immediately interrupted for contacts still in the queue.

[CAPTURE: Show the progress bar with the X icon highlighted.]

Important: Only contacts who have not yet started the flow will be affected. Contacts who already entered the flow will continue as normal.

4
Monitor and cancel a broadcast that is still sending

Broadcast messages follow a similar queued sending process.

To monitor broadcast progress:

  • Navigate to the Broadcasts tab
  • View the active broadcast’s sending progress

[CAPTURE: Show the Broadcasts tab with an active broadcast and progress indicator.]

To cancel a broadcast that is still sending:

  • Click the X icon to stop the broadcast
  • Send a corrected broadcast afterward if needed

Note: You cannot send another broadcast to the same group until the current one is completed or cancelled.

5
Know what happens after cancellation and key limits

When you cancel a flow start or broadcast:

  • Contacts who already received the message are not affected
  • Contacts still in the queue will not receive the message or start the flow
  • The action applies only to the remaining unsent contacts

Important limits to keep in mind:

  • Messages can only be sent as fast as your channel provider allows
  • If a sending queue takes more than 48 hours, it will automatically stop
  • Large queues may indicate channel-level throughput limits

If sending is consistently slow, check with your service provider to confirm your channel’s rate limits.

Common Issues

I clicked X but some contacts still received the flow or broadcast

Explanation: Contacts who had already started the flow or already received the broadcast before you cancelled are not affected.

Result: Only contacts still waiting in the queue are stopped.

I can’t send a new broadcast to the same group

Cause: A broadcast to that group is still in progress.

Fix: Wait for the current broadcast to complete or cancel it using the X icon, then send the new broadcast.

Sending is extremely slow

Cause: Your channel provider may have low throughput (messages per second) or temporary congestion.

Fix: Confirm provider rate limits, reduce send size, or consider distributing sends over time.

The send stopped by itself

Cause: If a sending queue takes more than 48 hours, it automatically stops.

Fix: Split large audiences into smaller batches or confirm throughput with your provider.