Message failed or the customer did not receive it
Distinguish backend acceptance, channel delivery, and final customer receipt.
Updated 2026-07-17
A message normally travels through YundaDesk, a channel adapter, and an external platform. A message bubble or an “accepted” status does not always mean the customer received it.
Troubleshooting order#
- Open message details and review send, delivery, and failure states.
- Check that the channel is online and authorization has not expired.
- Confirm that the recipient identity and conversation belong to the correct channel.
- Retry once from the Inbox; avoid repeated clicks that could create duplicates.
- Verify the result in Telegram, the website widget, or the actual customer client.
Common symptoms#
- Visible before refresh, missing afterward: A temporary UI message may not have been persisted. This is not a successful send.
- Marked sent, not received: Check final channel delivery and external platform restrictions.
- Several AI replies to one message: Stop AI reception for that conversation and report the message times and trace.
- A Yuna action times out: Check whether a real side effect already occurred before confirming again.
When contacting support, provide the workspace, channel, conversation, time, message summary, and delivery details. Never send a Bot Token, API key, or sensitive customer content.