Error 131060: unsupported message on a Coexistence number
Error 131060 arrives in a messages webhook as a message of type unsupported titled "This message is currently unavailable." On a Coexistence number Meta calls it expected: it happens mostly when someone writes to the business for the first time, often right after tapping a Click-to-WhatsApp ad, and usually clears within seconds. The message itself is readable in the WhatsApp Business app.
easyCoexistence keeps unsupported messages out of your automations, so your AI never answers a message it cannot read, and still forwards Meta's payload to your system when a Forward URL is set.
Meta's code for an incoming message that is currently unavailable, titled "This message is currently unavailable."
Meta says the error typically resolves within a few seconds, after which WhatsApp delivers messages normally.
The main scenario Meta names: a WhatsApp user messaging the business for the first time, common right after a Click-to-WhatsApp ad tap.
A different code in the same webhook: the Cloud API does not support that message type at all.
easyCoexistence automations do not run on an unsupported message; the next readable message from that chat starts them.
What does the 131060 webhook contain?
It is an ordinary messages webhook whose message has "type": "unsupported" and an errors array. The error carries code 131060 and the title "This message is currently unavailable.", with the same sentence as its message. An unsupported object names the kind of content Meta could not pass on; Meta's list of values includes image, interactive, reaction and poll_creation. There is no text body and no media id, so nothing in the payload tells you what the customer wrote. The sender's number, the message id and the timestamp are present as usual.
{
"object": "whatsapp_business_account",
"entry": [{
"id": "<WABA_ID>",
"changes": [{
"field": "messages",
"value": {
"messaging_product": "whatsapp",
"metadata": {
"display_phone_number": "<BUSINESS_NUMBER>",
"phone_number_id": "<PHONE_NUMBER_ID>"
},
"contacts": [{ "profile": { "name": "Ana" }, "wa_id": "5511999998888" }],
"messages": [{
"from": "5511999998888",
"id": "wamid.HBgN...",
"timestamp": "1762876800",
"type": "unsupported",
"errors": [{
"code": 131060,
"title": "This message is currently unavailable.",
"message": "This message is currently unavailable."
}],
"unsupported": { "type": "<UNSUPPORTED_TYPE>" }
}]
}
}]
}]
}Why does it happen on a Coexistence number?
Meta's Coexistence guide says partners "may receive an unsupported messages webhook with error code 131060" and that this is expected. It names two scenarios.
The first is a WhatsApp user writing to the business for the first time, which Meta says is especially common when someone taps a Click-to-WhatsApp ad and sends a message at once. The second is a WhatsApp user on an unsupported companion device sending a message to the business or receiving one from it.
Meta does not explain the mechanism. What it does say matters more: the error typically resolves within a few seconds, and after that WhatsApp delivers messages normally.
What should the business do when one arrives?
Read it in the app. Meta's instruction to platforms is to tell the business to check the WhatsApp Business app for the message, because the app on the phone has it even when the API copy was unavailable.
In practice: open the chat on the phone, read what the customer wrote and answer from there, or wait for the customer's next message, which normally arrives through the API without the error. Answering from the phone also tells automations that a person has the chat. For an ad campaign, expect a small burst of these at the start of new conversations rather than a fault.
How should your software and your AI handle it?
Treat it as a known event, not as a failure. Acknowledge the webhook with a 200, as you would for any delivery, so Meta does not redeliver it. Record the message id and the sender, which lets you link it to the conversation that follows. Never hand the empty message to an AI as if it were text: with no content, any reply is a guess. And alert on the rate of 131060 events, not on single ones.
- Return 200 quickly and deduplicate on the message id, as for any webhook.
- Skip AI replies and keyword matching for type unsupported.
- Show your team that a message is waiting in the app on the phone.
- Count 131060 separately from real failures in your dashboards.
Do automations run on an unsupported message?
On easyCoexistence, no. Automations read text, button and list replies, media captions and placeholders such as "[voice message]"; a message of type unsupported has none of these, so no automation answers it and no run appears. If a Forward URL is set, your system still receives Meta's original payload, error included. In direct mode, Meta sends it straight to your server.
The next readable message from that person starts automations as usual. Because nothing was stored for that chat yet, a "First message" automation, such as a welcome reply, answers that next message.
How is 131060 different from 131051?
Both arrive as type unsupported in the same messages webhook, which is why they get confused in logs. They mean opposite things for planning: one is a short gap that fixes itself, the other is a permanent limit of the API for that content. Read errors[0].code, not the type, to tell them apart in your handler. The table sums up what Meta's references say about each code.
| 131060 | 131051 | |
|---|---|---|
| Title | This message is currently unavailable. | Message type unknown |
| Meaning | The message cannot be passed on right now | The Cloud API does not support that type |
| Typical cause | First contact on a Coexistence number, often after an ad tap | Content the API never delivers |
| How long | Usually clears within seconds | Permanent for that content |
| What to do | Read it in the WhatsApp Business app | Ask the customer for text, or read it in the app |
Common mistakes
- Alerting on single 131060 events. Meta calls them expected on Coexistence numbers; watch the rate instead.
- Letting an AI reply to the empty message. The payload has no text, so the answer would be invented.
- Answering the webhook with an error status. Meta redelivers webhooks that fail, so one unsupported message turns into several deliveries.
- Assuming the message is lost. It is in the WhatsApp Business app; only the API copy was unavailable.
The number stays in the app on the phone, where the original message can be read. US$ 9 down to US$ 0.75 per number per month, falling as you add numbers, with the first 3 days free.
easyCoexistence is a multichannel API and MCP server that connects AI agents such as Claude and ChatGPT to WhatsApp, Instagram, TikTok, Facebook and more. On WhatsApp it uses Coexistence: the business keeps using its number in the WhatsApp Business app while the AI works through Meta's official API.
Frequently asked questions
Can I fetch the original content through the API?
Meta's guidance for 131060 is to check the WhatsApp Business app. Its webhook reference does not describe a way to retrieve the content later.
Does 131060 mean the number is broken?
No. If messages from regular contacts keep arriving as 131060 for hours, ask your AI to run get_number_health or check the connection, but bursts on first contact are expected.
Does it happen on numbers that only use the Cloud API?
Meta describes the first-contact pattern in its guide for numbers onboarded with the WhatsApp Business app, which is what Coexistence is. The code itself sits in Meta's general webhook reference, so handle it the same way on any number.
Is anything billed for it?
It is an incoming message. Meta bills the business for messages it sends, per message, by category and country, on its own WhatsApp Business Account.
Keep reading
Ready to get started?
Set up WhatsApp Coexistence in minutes, not months. The app keeps working on the phone.
Start Free TrialVerified on