Docs / Broadcasts / Broadcast failures and retries

Broadcast failures and retries

Last updated: 16 July 2026

Most broadcast failures are temporary and resolve themselves: Stravax Engage retries a message automatically after a transient issue, and it sends exactly once, never twice, once the retry succeeds. A smaller set of failures are permanent and settle immediately instead of being retried pointlessly. Your wallet balance is not one of the reasons a broadcast stops: Meta bills your own WhatsApp Business account directly at Meta's prices and Stravax Engage adds 0% markup, so a broadcast message does not draw from the wallet and sending keeps working whatever your balance is.

What happens when a message fails temporarily?

If a message fails for a reason a retry can fix, such as a brief hiccup writing to the billing ledger, Stravax Engage releases what it had claimed for that attempt and retries. When the retry succeeds, the message sends exactly once and is charged exactly once. If a message somehow gets redelivered after it already succeeded, that redelivery is a no-op, it doesn't send or charge again.

What happens when a message fails permanently?

Some failures aren't worth retrying. The campaign report keeps a skipped (insufficient credits) count next to the genuine delivery failures, so a money-shaped skip could never masquerade as a WhatsApp problem; at 0% markup nothing per message is charged to your wallet, so that count stays at zero and no top-up is needed to finish a campaign. A message that fails for a real delivery reason and is retried repeatedly but still can't go out is eventually marked permanently failed rather than being retried forever, and any amount already charged for it is refunded, along with releasing whatever sending budget had been reserved for it.

What if sending gets interrupted mid-message?

On the rare occasion something interrupts the system while a message is actively sending, Stravax Engage runs an automatic check for messages that have been stuck mid-send for an extended period. Genuinely stuck ones are marked failed and refunded; a message that's still legitimately in progress is left alone and not falsely marked as failed.

Where do I see what happened?

Open the broadcast itself to see how many of its messages sent, failed, were skipped for insufficient credits, or are still pending. A failed message is never left ambiguous, it's reflected in the campaign's own counts, and any charge tied to a message that ultimately failed is refunded rather than staying billed against you. A refund for a message that WhatsApp accepted but later reported as failed settles automatically shortly after the failure report arrives.

Related

More in Broadcasts