Troubleshooting
Number restricted or banned
How to recognize and handle a number restricted, blocked or banned by Meta.
Each symptom below follows the same shape: what you see, the cause and what to do.
Where to look
Section titled “Where to look”On the connection page, Overview tab, the Health card shows:
- Quality, Messaging tier and Speed;
- Sending: Available, Limited or Blocked;
- Restriction, with its end date (
Until {date}) or “No end date given”; - the What is blocked or limited list, grouped by Number, WhatsApp account, Business and App, each item with Meta’s code, description and suggested solution;
- What still works.
Messajo reads health every 15 minutes. Refresh health reads it right away.
The connection shows Restricted or Disabled
Section titled “The connection shows Restricted or Disabled”| Status | Reason (reason) |
What to do |
|---|---|---|
| Restricted | account_restriction: Meta restricted the account for a period |
Wait for the period and fix the cause in WhatsApp Manager |
| Restricted | policy_blocked: Meta blocked a send due to policy (368 or 131031) |
Same |
| Disabled | violation:<type> or banned |
Appeal at Meta. If Meta reinstates it (reinstated), the connection goes back to Active on its own |
| Active | restriction_lifted: the restriction ended |
Nothing |
scheduled_for_disable warns in advance: Meta scheduled the account to be disabled, with no status change.
While the connection is restricted, sends return 403 policy_blocked or 409 connection_restricted. When disabled, 409 connection_disabled.
Sending Limited or Blocked, with no status change
Section titled “Sending Limited or Blocked, with no status change”The connection stays Active, but Sending changed. Messajo emits connection.updated with reason can_send_changed. The cases the panel explains:
- No payment method (code
141006): the business cannot start conversations (templates). Replies to customers who wrote in the last 24 h keep working. Action: Add a payment method at Meta Business. - Business not verified (code
141010): lower sending limits. Sending within the current limit keeps working. Action: verify the business.
For the send error caused by a missing payment method, see also meta_payment_required.
Quality or messaging tier changed
Section titled “Quality or messaging tier changed”Messajo emits connection.updated with reason quality_changed (quality) or limit_changed (messaging tier or capacity). Understand the tier in Meta messaging limit.
Spam signals on sends
Section titled “Spam signals on sends”429meta_spam_rate_limited(Meta131048): many messages from the number were reported or blocked. Do not resend. Campaigns pause on their own. Review the list (only people who opted in), the template content and the frequency, and wait for quality to recover.422marketing_limit_reached(Meta131049): Meta held the marketing template to protect the contact’s engagement. Do not resend right away.
What Messajo does on its own
Section titled “What Messajo does on its own”- Emails owners and admins on each status change (at most one per reason every 6 h).
- Emits
connection.*events with the reason inreason.
What Messajo does not do
Section titled “What Messajo does not do”It does not lift a restriction or reverse a ban. Appeals and disputes happen in Meta’s tools, in WhatsApp Manager.
Get notified in your system
Section titled “Get notified in your system”Create a global destination that subscribes to connection events:
{ "connection_id": null, "event_types": ["connection.*", "org.*"] }Each event carries data.connection.status, previous_status and reason. The full table is in Connection reasons.