TL;DR: WhatsApp error 131064 means your account has reached a messaging limit because of repeated template classification violations (templates categorized incorrectly, e.g. marketing content submitted as utility). Meta's
detailsstring is "Message failed to send because this account has reached its messaging limit due to template classification violations. This applies to both template messages and direct send messages." Meta caps the WABA's utility message volume for at least 7 days and lifts the cap once categorization improves; marketing and authentication sends are not affected.
What Error 131064 Means
131064 is a throttling/enforcement error. When a business repeatedly misclassifies template categories (Marketing / Utility / Authentication), Meta applies a progressive messaging limit. Meta's official details value is:
"Message failed to send because this account has reached its messaging limit due to template classification violations. This applies to both template messages and direct send messages."
Meta's template categorization guidelines (updated September 15, 2026) describe this as the rate-limiting level of its misuse enforcement. Utility message volume on the WABA is capped within a rolling 24-hour window, and utility sends over the cap are rejected, whether sent as normal template messages or through direct send. Marketing and authentication messages are not affected. The cap lasts at least 7 days and is lifted once categorization quality improves. Older third-party summaries described it as blocking every send on the account; Meta's current guidelines limit it to utility volume.
Meta announces it with an account_update webhook: violation_type: UTILITY_TEMPLATE_ABUSE_RATE_LIMIT with restriction_type: RATE_LIMITED_UTILITY_TEMPLATE_MESSAGING, and UTILITY_TEMPLATE_ABUSE_RATE_LIMIT_RECOVERY when the cap is removed.
Where You See It
Synchronous /messages response when you send a utility template over the cap. The cap covers all utility volume on the WABA, not just one template.
Common Causes
- Submitting marketing content under a utility or authentication category to dodge pricing/limits.
- Repeated category-correction strikes after Meta re-categorized your templates.
- A pattern of misclassification across multiple templates pushing the account past the enforcement threshold.
How to Fix It
- Review every template's category in WhatsApp Manager and confirm content matches the category (promotional → Marketing; transactional/account updates → Utility; OTP → Authentication).
- Re-create or re-categorize misclassified templates correctly.
- Wait out the enforcement period (at least 7 days). Meta lifts the cap once categorization improves. To dispute individual recategorized templates, request a review in Business Support → Template category updates.
- See Meta's Template quality and Template categorization docs for category rules.
How to Prevent It
- Categorize honestly at creation; don't label marketing as utility.
- Monitor
template_category_updatewebhooks so you know when Meta re-categorizes a template. - Periodically audit template content against current categorization guidelines.
Related Errors
- WhatsApp Error 131048 — spam rate limit (quality-based).
- WhatsApp Error 131049 — per-user marketing frequency cap.
- WhatsApp Error 368 — account restricted for policy violations.
- WhatsApp Webhook Override (Error 100)
- See the full error reference
FAQ
Q: Does 131064 only block the bad templates? A: No. It caps all utility volume on the WABA, whether sent as template messages or through direct send. Marketing and authentication messages are not affected.
Q: How long does 131064 last?
A: At least 7 days. Meta lifts the cap once categorization quality improves, so fix classifications and watch for the UTILITY_TEMPLATE_ABUSE_RATE_LIMIT_RECOVERY webhook. Repeat misuse can lead to longer, wider restrictions.
Q: Can I appeal 131064? A: Not the cap itself; it lifts once categorization improves. You can appeal individual templates you think were wrongly recategorized in Business Support → Template category updates.
Q: What's a "template classification violation"? A: Submitting a template under the wrong category (commonly marketing content as utility/authentication); repeated strikes trigger progressive enforcement.
How Dualhook Helps
The trigger and fix live in your payload logic and Meta's tools. Dualhook relays the send without persisting its content and can surface template state and category-update signals, helping you spot misclassifications before they accumulate into a 131064 limit. The re-categorization itself is done in WhatsApp Manager. Dualhook shows the account_update restriction as an account alert and does not block the connection; Meta rejects the over-cap utility sends.