Delivery & Logs
Outcomes, the counters and the live activity log, and how Wexio paces sends
Once a broadcast is Sending, every send gets one of three outcomes. The counters on the broadcast add those outcomes up, and the Live activity log lists them one by one.
Outcomes
| Outcome | Meaning |
|---|---|
| Delivered | Wexio sent the message or flow and the channel accepted it. |
| Failed | Wexio tried to send and the channel or Wexio returned an error. |
| Skipped | Wexio did not try, because a condition was not met. |
A send is one contact on one channel. A contact on two channels has two sends, so the counters can add up to more than the audience. See Routing Across Channels.
Delivered means the channel accepted the message. Wexio does not record later delivery or read receipts on a broadcast. For Telegram the send is confirmed right away.
Failed Reasons
The log shows the reason next to each failed send. Typical ones:
| Reason | What to do |
|---|---|
| ops_limit_reached | You ran out of ops. Raise the limit or turn on usage credits, then retry. |
| Rate limited - too many retries | The channel kept refusing. Retry later. |
| processing_timeout | One send took over a minute. Retry. |
| A channel error such as a blocked bot | The contact cannot be reached. Do not retry. |
Skipped Reasons
Skipped sends are not retried, because the same setup would skip them again. Fix the cause and create a new broadcast.
| Reason | Cause |
|---|---|
| No chat found | The contact has no conversation to send to. |
| WhatsApp 24h window closed | The flow does not start with a template and you set no fallback for that WhatsApp integration. |
| Instagram 24h window closed | The contact must message you first. Instagram has no template fallback. |
| No template route configured | Template broadcast: the chat is on an integration without a route. |
| Chat not on a whitelisted integration | The chat is on a channel you left out in step 1. |
Counters
Select a broadcast to see its details.
| Item | What it shows |
|---|---|
| Delivered card | The share of the audience delivered, with a bar split into delivered, failed, skipped and pending. |
| Contacts | The audience size. It is the estimate until the broadcast starts, then the real count. |
| Delivered, Failed, Skipped | The number of sends with each outcome. |
| Pending | Sends not processed yet. A cancelled broadcast shows Cancelled here instead. |
The list shows the same progress per row, for example 1 / 324, with a percentage bar.
Live Activity
Click Live activity in the details to open the log. While the broadcast is Sending it shows Live and new rows appear as they happen. When it is over the button reads Open delivery log.
Each row shows the time, the outcome, the contact and the reason if there is one. Click a row to expand it and see the contact and chat ids, when it was dispatched and when it was sent. Use the contact and chat links to open them. Use the filter to show All, Delivered, Failed or Skipped rows. With no rows yet the log says No dispatches yet - events appear here in real time.
If too many rows arrive at once, some are dropped from the live view and the log shows Too many new rows, some were dropped. Reload. Click it to reload the full list.
Rows are kept for 30 days. The counters on the broadcast stay.
Pacing
Wexio does not send to the whole audience at once. It sends in batches and slows down on its own when a channel limits how fast it accepts messages. You do not set a rate. Large audiences take longer, and the broadcast stays Sending until the work is done.
- Rate-limit pauses are not failures. When a channel asks Wexio to wait, Wexio waits and tries again. The contact is Delivered once it works.
- Retries are limited. After 5 tries a contact fails with Rate limited - too many retries.
- WhatsApp tier limits are Meta's. Meta caps how many people you may message in a day. Wexio does not check that cap for you.
If a run takes much longer than you expect, check the integration in Settings → Integrations.
Ops
Each delivered send uses 1 op. If your plan has no ops left and usage credits are off, the send fails with ops_limit_reached, and the broadcast still ends Completed. See Ops Usage.
Reading the Numbers
All delivered. A healthy run.
Many skipped. Look at the reasons in the log. WhatsApp 24h window closed means you need a fallback template. No template route configured means you need more routes or a tighter audience.
Failed with the same reason. Fix that cause, then retry the failed contacts.
Related
- Fallbacks & Template Routes: how fallbacks and routes decide what each contact gets.
- Retry Failed Contacts: send again to the failed sends.
- Lifecycle & Cancellation: statuses and what happens to stuck broadcasts.