Troubleshooting broadcasts: failures, missing identity, unapproved template, stuck, retries
Diagnose and fix the most common broadcast errors: failed recipients, contacts without a WhatsApp identity, unapproved templates, stuck sends and retries.
What this guide covers
When a campaign doesn't deliver as expected, the cause is almost always one of five things. This guide helps you spot the problem from the broadcast detail screen and fix it.
To start, go to Broadcasts, open the affected campaign and check the stats panel: you'll see the Sent, Delivered, Read, Replied and Failed counters. Every failed recipient stores an error reason — that's your best clue.
1. Failed recipients
- Open the campaign under Broadcasts and look at the Failed counter.
- Read the error reason on each failed recipient.
- The usual causes are: an invalid number, a closed 24-hour window (not applicable to templates), or a Meta rejection (131xxx codes).
Tip: if every send fails with OAuthException code 190, the channel token has expired. Reconnect your WhatsApp channel from Settings → Channels using Embedded Signup.
2. Contacts with no identity
A contact without a valid WhatsApp identity cannot receive the message and shows up with Contact not found or an invalid-number error.
- In the Audience step of the wizard, the Estimated recipients counter counts every contact matching your filters; it does not check that each one has a valid number or channel identity. Those contacts are skipped at send time and end up as Failed.
- Make sure contacts have a number in international format with a
+prefix. - Clean up your segment (group, tag or custom field) so it doesn't pull in incomplete records.
3. Unapproved template
WhatsApp broadcasts can only use templates approved by Meta.
- In the Message step, the WhatsApp Template picker only lists approved templates.
- If you don't see your template, its status is pending or rejected. Check it in the channel's template manager.
- If a template is rejected after you schedule the campaign, the send fails with "WhatsApp template is not approved". Swap it for an approved one and create the broadcast again.
4. Stuck campaign
If the status stays on Sending for a long time:
- Confirm you haven't hit your plan's monthly recipient cap. Once reached, remaining recipients are marked failed with "Plan cap reached".
- Check you haven't hit another plan cap (broadcasts per month or recipients per send). Broadcasts are on all plans, but the WhatsApp via QR channel doesn't allow them.
- Give it a few minutes: sending is batched and respects Meta's throughput limits.
5. Retries
Each message is retried automatically up to 3 times with a growing wait. Only after the third failed attempt is the recipient permanently marked Failed. There's no need to retry by hand: read the reason, fix the cause (template, number or token) and launch a fresh campaign to the failed recipients.
Verify
Go back to the campaign detail and confirm that Delivered + Read climb while Failed stops growing. A healthy delivery rate sits above 90%.
Related articles
Related articles
-
How to create a broadcast campaign
Create, segment and schedule a broadcast to your contacts step by step in Omnifox.
-
Best practices to broadcast without getting blocked
Reduce spam reports and blocks by following these rules when sending broadcasts on WhatsApp and other channels.
-
What a campaign is and its statuses (draft, scheduled, sending, completed)
What a broadcast campaign is in Omnifox and what its statuses mean: draft, scheduled, sending and completed.
-
Supported broadcast channels (WhatsApp, Email, SMS, Telegram)
Learn which channels you can use to send broadcasts in Omnifox and what each one requires.
-
Segment your audience: everyone, groups, tags (AND/OR) and custom field
Learn to precisely choose who receives your broadcast by combining groups, tags with AND/OR logic and custom fields.