TL;DR: WhatsApp error
131000is Meta's generic "something went wrong" bucket for sends that failed without a more specific public code. Retry cautiously if it looks transient; if it persists, capturefbtrace_id, timestamps, and payloads and open support.
What Error 131000 Means
Meta's current title is "Something went wrong"; older docs and threads describe the same code as "Message failed to send due to an unknown error." The practical meaning is unchanged: the request failed without a more specific publicly-exposed root-cause code. (Title wording is a search-vocabulary note; treat the generic-failure meaning as the stable basis.)
Where You See It
Both ways — an immediate API error and a failed status webhook after the send appeared accepted, which is part of why it causes confusion.
Common Causes
- Temporary Meta-side processing issues or generic backend failures.
- An account/template/send condition that didn't map to a more specific public code.
- Cases where the send path and the final delivery path disagree.
How to Fix It
- Determine whether the problem is broad or isolated.
- If transient, retry with capped backoff and jitter.
- If it persists, capture
fbtrace_id,wamid, full request/response metadata, and the failed webhook payload. - Reproduce with a known-good recipient and template before changing unrelated code; open Meta support if it's sticky or widespread.
How to Prevent It
- Log every send with full Meta error metadata; build idempotent retry logic.
- Separate retryable transient failures from dead-letter/manual-investigation failures.
- Don't rely only on the initial API response.
Related Errors
/docs/whatsapp-error-131026— undeliverable recipient/docs/whatsapp-error-131031— account locked/docs/whatsapp-error-132001— template lookup failure- See the full error reference
FAQ
Is 131000 retryable? Sometimes — if clearly transient. If it repeats, investigate and escalate rather than hammering retries.
Why did the title change from "unknown error" to "something went wrong"? Meta updated the public wording; the code is the same generic failure bucket.
What should I send to Meta support? At minimum fbtrace_id, wamid, UTC timestamp, the endpoint used, and whether the failure arrived in a webhook.
How Dualhook Helps
This is a send-side symptom; Dualhook is not in the message-content path and can't diagnose your payload. It reduces guesswork by giving you API Errors, Messaging Health Status, and Maintain Account Health context — helping you separate "generic transient" from "generic symptom of a real account issue."