A broadcast slows down at your number's sending limit

Released 24 September 2026

When your WhatsApp number is at its sending limit, a broadcast now waits and tries again instead of failing the rest of your list straight away.

What's new

• It waits, then tries again. When WhatsApp says the number is at its sending limit, WA.cr holds the broadcast and then tries again. This can happen when another provider or app sends from the same number.
• The wait grows with the limit. The first wait is about a minute. The longer the number stays at its limit, the longer WA.cr waits between tries, up to about 15 minutes.
• No one is skipped while it waits. The message WhatsApp refused goes out first when the broadcast carries on, and the rest of the list waits its turn.
• It stops cleanly after 2 hours. If the number stays at its limit for 2 hours, WA.cr stops the broadcast. The people it didn't reach are marked failed, and you aren't charged for them. Retry failed sends it to them later.
• The report tells you. While it waits, the broadcast's report shows Slowed, when WA.cr tries again and when it would stop. A stopped broadcast says Stopped at the sending limit.
• Broadcasts from the API work the same way. They now go out in the background like the ones you send in WA.cr, with the same retries, waits and stop. The API now answers as soon as the broadcast is queued, before anything is sent: follow it with GET /v1/broadcasts/{id}.
• Fewer false failures. A limit on how often WA.cr can send requests to WhatsApp used to count as a permanent failure. Now it slows the broadcast down too.

Open Broadcasts and pick a broadcast to see its report. Using your number with another provider? See Use your number with another provider.