- Joined
- Sep 9, 2024
- Messages
- 20
- Reaction score
- 19
Hi all,
We're using 3CX with WhatsApp integration and we're encountering an intermittent error in the logs:
Error: Unable to parse message from provider whatsapp. Error: Cannot find valid routing for incoming Whatsapp message to number: +3xxxxxxxxxx
This happens randomly – most messages are received and routed correctly, but occasionally this error appears, and the message is not delivered to any destination.
Here are some details:
* The number `+3xxxxxxxxxx` is properly configured and routed in 3CX under *Messaging → WhatsApp*.
* The destination is set to a queue (we’ve also tested with a user and a chat flow – same behavior).
* No recent changes to WhatsApp configuration.
* We're on 3CX Version 20.0 Update 6 (Build 486 Alpha).
* The error is not tied to a specific message type (e.g., it happens with plain text too).
* Webhook status from the provider side appears OK.
Has anyone else experienced this issue? Could it be a delay in webhook delivery or some unsupported message format? Any insights or fixes would be appreciated!
Thanks in advance.
We're using 3CX with WhatsApp integration and we're encountering an intermittent error in the logs:
Error: Unable to parse message from provider whatsapp. Error: Cannot find valid routing for incoming Whatsapp message to number: +3xxxxxxxxxx
This happens randomly – most messages are received and routed correctly, but occasionally this error appears, and the message is not delivered to any destination.
Here are some details:
* The number `+3xxxxxxxxxx` is properly configured and routed in 3CX under *Messaging → WhatsApp*.
* The destination is set to a queue (we’ve also tested with a user and a chat flow – same behavior).
* No recent changes to WhatsApp configuration.
* We're on 3CX Version 20.0 Update 6 (Build 486 Alpha).
* The error is not tied to a specific message type (e.g., it happens with plain text too).
* Webhook status from the provider side appears OK.
Has anyone else experienced this issue? Could it be a delay in webhook delivery or some unsupported message format? Any insights or fixes would be appreciated!
Thanks in advance.
