TL;DR: WhatsApp error
131056("pair rate limit hit") means you sent too many messages from your business number to the same recipient in a short period. It's not an account block — pace your per-recipient sends and back off; you can still message other numbers immediately.
What Error 131056 Means
Meta's details string is: "Too many messages sent from the sender phone number to the same recipient phone number in a short period of time." (Throttling error — confirmed verbatim on the live table; the full message form is "(#131056) … pair rate limit hit", HTTP 429.) It's a per-pair safeguard distinct from account-wide throughput. Meta's solution text: "Wait and retry the operation, if you intend to send messages to the same phone number. You can still send messages to a different phone number without waiting."
Where You See It
An immediate API error (HTTP 429) on the send call; it can also appear in tool error dashboards. The root condition is send-time per-pair throttling.
Common Causes
- Rapid back-to-back messages to one recipient.
- Multiple separate messages (confirmation + tracking + survey) fired together.
- Retry loops or several workers racing to message the same user.
How to Fix It
- Pause and retry that recipient with backoff. Meta's guidance is "wait and retry"; Dualhook's reference additionally recommends a
4^X-seconds backoff per retry (this is a Dualhook recommendation, not Meta's wording). - Keep sending to other recipients — only the pair is throttled.
- Bundle multiple updates into fewer, richer messages.
- Audit parallel workers so only one drains a given recipient queue at a time.
How to Prevent It
- Queue messages per business-number/recipient pair (a token bucket per pair).
- Per Meta's platform docs, a business number can send roughly 1 message every 6 seconds to the same WhatsApp user; bursts are possible but borrow against future quota, so "it worked once" isn't a safe design.
- Make retries pair-aware, not only globally rate-limited. See Capacity, Quality & Limits.
Related Errors
/docs/whatsapp-error-130429— per-number throughput limit/docs/whatsapp-error-131048— spam-rate restriction/docs/whatsapp-error-80007— WABA management rate limit- See the full error reference
FAQ
What is WhatsApp error 131056? Too many messages to the same user too quickly.
Is my account blocked? No — only the specific business↔user pair is throttled.
Is 131056 the same as 130429? No — 131056 is recipient-pair specific; 130429 is broader send throughput.
Will generic exponential backoff fix it? Only if retries are keyed to the same recipient pair; otherwise parallel workers recreate the problem.
How Dualhook Helps
This is a send-side pacing problem fixed in your backend caller. Dualhook relays each requested send once and never automatically retries it, so your application must pace or retry deliberately. Dualhook documents the per-recipient limit and back-off guidance in Capacity, Quality & Limits and surfaces failed statuses for visibility.