Error 131000 means the message failed to send for a reason Meta does not name. It is usually temporary. Try the send again; if it keeps failing across several attempts and several recipients, check Meta's platform status and send us the exact error text.
Symptom
A single message, or a run of messages, fails with 131000 and no further detail. Other messages sent at the same time may succeed.
Why it happens
- Meta returns 131000 when its own side fails without a more specific code, for example a short interruption while handling the request.
- For WhatsApp Flows that call your own endpoint, Meta's guidance adds that a wrong public-key signature step, a failing GraphQL call or a bad response from your endpoint can also surface as 131000.
Fix
- Try the send once more after a minute. A one-off 131000 usually clears on retry.
- If one recipient fails every time and others do not, try a different message type to the same person and check whether the number is on WhatsApp (see error 131026).
- If many recipients fail together, look at Meta's WhatsApp Business Platform status page before retrying in bulk.
- If you use a WhatsApp Flow with an endpoint, check that your endpoint answers within the time Meta allows and returns the expected encrypted response.
- If it persists after a few attempts, contact us with the error text and time. Open Support in the app and send the exact error text, the time and the number it happened on; the thread keeps the history.
In VGraple CRM
VGraple CRM shows the code and Meta's own text on the failed message in the inbox and in the broadcast report. A failed broadcast row can be retried with Retry failed, and a single inbox message can be sent again.
Related errors
All codes are listed in the WhatsApp error codes reference.