Retry Failed Contacts
Create a new broadcast that sends again to only the contacts that failed
Some contacts fail in any broadcast, for example a blocked bot or a provider error. Retry failed creates a new broadcast for exactly those contacts, so you do not rebuild the audience.
When the Button Appears
The Retry failed (N) button shows on the broadcast details when all of these are true:
- The status is Completed or Failed. It does not show for Scheduled, Sending or Cancelled broadcasts.
- At least one contact has the Failed outcome. N is that number.
- Your role can edit broadcasts. Agents do not see it.
Sends with the Skipped outcome are not retried. They were skipped for a reason such as no chat on a route integration, and a retry would skip them again. Fix the cause and create a new broadcast instead. See Delivery & Logs.
Retry a Broadcast
- Open the broadcast and click Retry failed (N).
- In the Retry failed contacts? dialog, check the number. It reads Create a new broadcast targeting just the N failed contacts.
- Click Retry now.
Wexio shows Retry scheduled, creates a new broadcast named Retry: followed by the original name, and schedules it for about 2 minutes later. The details of the new broadcast open.
- Same content. It uses the same flow or template, fallbacks, routes and channels as the original.
- Fixed audience. It sends to the list of contacts that failed. It does not run the audience filter again.
- Linked. The new broadcast shows a View source link that opens the original.
The original broadcast does not change.
Retries Count Toward the Quota
A retry is a new broadcast, so it counts toward the combined quota while it is Scheduled. If you are at the cap, cancel something first. If it fails you see Failed to schedule retry.
Retry More Than Once
You can retry a retry. Each one targets only the contacts that failed in the one before. Stop when no contacts fail, or when the rest fail for a reason a retry cannot fix.
When to Retry
Retry helps when the cause is temporary or you have fixed it.
| Cause | What to do |
|---|---|
| A provider error or rate limit | Retry. |
| ops_limit_reached: you ran out of ops | Raise the limit or turn on usage credits, then retry. |
| A broken integration connection | Reconnect the integration, then retry. |
| A closed WhatsApp 24 hour window and no fallback | Create a new broadcast with a template fallback. The retry reuses the original setup. |
| A template or media error | Fix the template, then create a new broadcast. |
| The contact blocked your bot | Do not retry. The same error comes back. |
Per-Contact History Is Kept for 30 Days
Retry reads the per-contact history, which Wexio keeps for 30 days. After that, the failed contacts are gone and retry fails because there is nothing to retry. The totals on the broadcast stay.
To redrive an older broadcast, create a new one with the same audience filter. That reaches everyone again, not only the failures.
Related
- Delivery & Logs: the outcomes and the history table.
- Lifecycle & Cancellation: which statuses allow which actions.
- Limits & Permissions: the scheduled quota and who can retry.