WhatsApp error 131056: too many messages to one recipient

Why it is per pair

Because the failure it protects against is not volume in general, it is one person being flooded. An account can be well within its overall throughput while sending thirty messages to one recipient in a minute, and the person on the other end experiences that as spam regardless of the account's total.\n\nThe limit therefore applies to the pair rather than the account, which is why it can appear on a low volume number that has never come near its overall rate limit.

What usually causes it

Almost always something automatic rather than a person typing.

• A retry loop that treats a delivery failure as a send failure and sends again.
• A webhook handler that sends a reply and is invoked more than once for the same event.
• A chatbot splitting one response into many short messages in quick succession.
• A test script sending to the same number repeatedly during development.

How to avoid it

By throttling at the conversation level rather than only at the account level. A limit on messages per recipient per minute, applied before the send, costs almost nothing and prevents both this error and the customer experience behind it.\n\nMessage deduplication matters as much. Webhook events can be delivered more than once, and a handler that sends a reply without checking whether it already handled that message id will produce exactly this pattern under load.

Common mistakes

• Retrying, which sends yet another message to the recipient already being flooded.
• Throttling only at the account level. This limit is per recipient.
• Handling webhook events without deduplicating by message id.

Frequently asked questions

Keep reading