Coexistence FAQs & Troubleshooting
This guide covers important error and their troubleshooting approach during Coexistence use
Unsupported Message Type Error in Coexistence
Error codes: 131051, 131060, and others
If you're using WhatsApp Coexistence to connect your WhatsApp Business App number to Chakra Chat, you may occasionally see a message in your inbox that says something like:
"Unsupported message. View in WhatsApp Business App."
This is expected behavior in certain situations and is enforced by Meta, not a bug in Chakra. This guide explains why it happens, what the different error codes mean, and what you can do about it.
What this error means
An "unsupported message" placeholder appears in Chakra when a message sent or received on your Coexistence number can't be relayed to Chakra through Meta's webhook system. The message still exists — it's just not visible in Chakra, because Meta never sent Chakra the data needed to display it.
This is a Meta/WhatsApp Cloud API limitation, not something Chakra can bypass. The original message is always still visible in the WhatsApp Business App itself.
Common error codes you may see
Error Code | Meaning | Typically appears when |
|---|---|---|
131051 | Unsupported message type | The contact sent a message type the Cloud API doesn't support at all (e.g. reactions, polls, disappearing/view-once messages, deleted messages) |
131060 | Message received during sync / unavailable | A Coexistence-specific limitation — usually tied to first-time messages, unsupported companion devices, or a number that's still syncing |
Others (no numeric code shown) | Generic "unsupported message" placeholder | Edited messages from a contact, or messages sent via an unsupported linked device |
Both codes point to the same underlying issue: Meta didn't send a webhook event containing the message content, so Chakra has nothing to display.
Why this happens
There are five common causes. Match what you're seeing to the scenario below.
1. Contact used an unsupported companion (linked) device
Meta supports most WhatsApp companion/linked devices in Coexistence, but WhatsApp for Windows and WhatsApp for WearOS are not supported. If your contact sends a message from one of these, it does not trigger a webhook, so Chakra can't mirror it. (Meta's linked devices documentation covers this in detail.)
2. Message sync after a period of inactivity
If a contact messages your Coexistence number after it's been inactive for a while, the connection may need a moment to refresh. Messages that arrive during this refresh window can show up as unsupported until sync completes.
3. Genuinely unsupported message type
Some WhatsApp message types simply aren't supported by the Cloud API, regardless of Coexistence. This includes things like reactions, polls, view-once messages, and deleted/revoked messages. These will always show as unsupported — there's no fix, since the Cloud API doesn't process this content at all.
4. First-time message, especially via a Click-to-WhatsApp ad
When someone messages your number for the very first time — particularly right after tapping a Click-to-WhatsApp ad — that first message may not arrive through the webhook. This is the scenario tied to error 131060 and is called out explicitly in Meta's documentation as expected behavior that typically resolves within seconds.
5. Contact edits a previously sent message
If a contact edits a message they already sent you, the edited version can also appear as unsupported in Chakra, even though the original came through fine.
What you can do
Cause | What to do |
|---|---|
Unsupported companion device | View the full message directly in the primary WhatsApp Business App on your phone. |
Sync after inactivity | Wait for sync to complete — subsequent messages should arrive normally. No action needed. |
Unsupported message type | View the message in the WhatsApp Business App. This is a permanent Meta limitation with no workaround. |
First-time message via ad | No action needed — this typically resolves within seconds as later messages come through normally. |
Edited message | View the edited message in the WhatsApp Business App. |
If you're seeing unsupported messages consistently, even for regular text messages from contacts on supported devices, that's not expected — see the troubleshooting note below.
When this might indicate a real connection issue
Occasional unsupported-message placeholders are normal with Coexistence. But if most or all incoming messages are showing as unsupported, check the following:
- Confirm the message is visible in the WhatsApp Business App on your primary device.
- Go to WhatsApp Business Manager and confirm Chakra is still listed as an active connected partner for your WhatsApp Business Account.
- If Chakra isn't listed, your partner connection has likely been removed — you'll need to reconnect your Coexistence Channel through the Embedded Signup flow.
A common cause of a dropped partner connection: the WhatsApp Business App wasn't opened on the primary device for 14+ days, which can log out linked devices and disrupt the connection.
Unsupported Message FAQ
Will I lose the message content permanently? No. The message is never lost — it's just not mirrored in Chakra. It remains fully visible in the WhatsApp Business App at all times.
Does this affect message delivery to my contact? No. This only affects whether Chakra can display the message. Delivery on WhatsApp itself is unaffected.
Is this a Chakra bug? No. This is a limitation enforced by Meta's Cloud API for Coexistence-connected numbers. It applies to every platform that offers Coexistence, not just Chakra.
Can I get history/contact syncing to avoid this? Contact and message history syncing during onboarding is separate from this issue and doesn't prevent unsupported-message placeholders from appearing for the five scenarios above.