WhatsApp error 131049: what it means and what to do

What does WhatsApp error 131049 mean?

Error 131049 is returned when Meta declines to deliver a marketing template message to one particular person. Meta's Cloud API error reference gives the description as "This message was not delivered to maintain healthy ecosystem engagement", and the recommended action as waiting at least 24 hours before resending (Meta — Cloud API error codes).

That sentence explains almost nothing, which is why the code is so widely misread. The ecosystem in question is not your account. It is the recipient's inbox.

131049 is also a delivery-time failure rather than a rejected API call. Meta accepts the send and hands back a message id; the failure arrives afterwards on the status webhook, because as Meta's webhook reference puts it, "Outgoing message errors appear in the statuses array" (Meta — webhook components). That is why this one usually surfaces as a campaign with a delivery rate nobody can account for. If the send-then-webhook shape is new to you, it is covered in our full guide to the platform.

• What does WhatsApp error 131049 mean?
• Is error 131049 caused by my template quality or my sender reputation?
• What are per-user marketing template message limits?
• What does Meta say to do about error 131049?
• Does retrying error 131049 make it worse?
• Why do marketing templates to US numbers never arrive?
• Is 131049 the same as the marketing message experiment?
• How do you hit error 131049 less often?
• What is the difference between WhatsApp errors 131049, 131047, 131048, 131026, 131050, 132015 and 130472?
• Are you charged for a 131049, and what does it do to reporting?

Is error 131049 caused by my template quality or my sender reputation?

Neither. Both are the natural guess, because almost every other Cloud API delivery failure does trace back to one or the other. For this code specifically, both are the wrong tree.

Meta's documentation on per-user marketing template message limits states that "WhatsApp may limit the number of marketing template messages a WhatsApp user receives from any business in a given period of time when they are less likely to be receptive and engage with those messages" (Meta — per-user marketing template message limits).

Read any business. The counter is attached to the person, and it counts marketing templates they receive from everyone — your competitor, their bank, the shop that sold them shoes last week. You can hit it with a freshly approved, well-written template, on your first send of the day, from a number rated Green.

Checked against Meta's developer documentation on 22 August 2026.

What are per-user marketing template message limits?

Meta does not publish the rule, only some of the inputs. It says WhatsApp "determines this based on several factors, including a dynamic view of an individual's recent marketing message read rate and how many messages they currently have in their inbox from friends, family, and businesses", and that the limit "adapts automatically over time based on a person's recent engagement levels" (Meta — per-user marketing template message limits).

Note several factors, including. Even the list of inputs is not complete.

Three things follow, and all three matter:

• Meta publishes no number. There is no documented cap of two, or five, or any other figure. Any page giving you one is guessing. A fixed number would not mean much anyway against a limit described as adaptive and per-person.
• It is scoped to marketing templates. Meta's page is written against marketing templates throughout and never mentions utility or authentication. It does not say in so many words that those categories are exempt, so treat the scope as strongly implied by Meta's wording rather than declared by it.
• It is not active everywhere. Meta states the limits are "not currently active for messages sent from a business phone number in the European Economic Area, United Kingdom, Japan, or South Korea, or to a WhatsApp user in these countries."

What does Meta say to do about error 131049?

One thing: wait. Meta's instruction is to "wait at least 24 hours before attempting to resend a marketing template message to a user that has reached their limit" (Meta — per-user marketing template message limits).

There is a second and far more useful route on the same page. Meta states: "If a WhatsApp user responds to a marketing message, it starts a 24-hour customer service window. Marketing messages sent within this window do not count towards the limit."

A reply is the reset button, and that is the whole design of the mechanism. It is built to make businesses earn a response rather than keep broadcasting into silence.

Does retrying error 131049 make it worse?

Yes, and Meta says so in as many words. If a WhatsApp Business account "attempts to resend marketing messages multiple times within a 24-hour period to users who have already reached their messaging limit, further delivery attempts to these users may be unavailable for up to 24 hours and error code 131049 will be returned" (Meta — per-user marketing template message limits).

So an automatic retry queue is not a neutral convenience here — it is the exact behaviour Meta describes as extending the block. Any retry schedule whose first attempt falls inside 24 hours works against the instruction printed on the same page.

WabaCRM does not automatically retry a 131049. The recipient is marked failed with Meta's code against them and the decision to send again is yours. If your platform retries failures automatically, find that setting and check what it does with this code specifically.

Why do marketing templates to US numbers never arrive?

A separate rule produces an identical symptom, and it is worth ruling out before hunting for a per-recipient explanation. Meta's per-user limits page states that "WhatsApp does not currently deliver marketing template messages to WhatsApp users with United States phone numbers (numbers composed of a +1 dialing code and a US area code)" (Meta — per-user marketing template message limits).

That is a blanket country rule, not an engagement limit, so waiting 24 hours does nothing. Note the precision in Meta's wording too — a +1 number with a US area code, which is not the same set as every +1 number. Meta does not name the error code returned here, so treat a wholesale US failure as a country question rather than assuming 131049 is doing the work.

Both the country rule and the regional exemptions carry the word currently in Meta's own text, which is Meta reserving the right to change them. Checked on 22 August 2026.

Is 131049 the same as the marketing message experiment?

No. Error 130472 is a different mechanism with the same outward symptom. Meta runs an experiment in which "a very small percentage of WhatsApp users do not receive marketing template messages from any business" unless a customer service window or a free entry point window already exists between that user and that business. Meta states that it "does not bill you for it", and that "a status messages webhook triggers with status set to failed" (Meta — experiments). Waiting does not clear it: it is not a limit the recipient fell under, it is a group they are in.

How do you hit error 131049 less often?

Partly, you do not. A limit attached to a stranger's inbox, adapting to their behaviour across every business that messages them, is not something a platform setting can reach. Anyone selling a fix for it is selling something Meta does not offer.

What is in your control is how often you are standing on the wrong side of it:

• Categorise honestly. An order update, a delivery notice or an appointment reminder is a utility template. Bolting a promotional line onto the end makes the whole thing marketing, and drags it under a limit it never needed to be under. This is the most common self-inflicted cause.
• Stop broadcasting to people who never reply. Read rate is one of the factors Meta names, so an unengaged segment is where the limit bites hardest — and it is the segment each attempt was worth least on anyway.
• Use the window you already have. Anyone who wrote to you in the last 24 hours can be answered with ordinary free-form messages, which Meta does not charge for inside an open window and which no marketing limit applies to.

For the wider picture of what caps your reach — messaging tiers, throughput, and the broadcast-list confusion underneath all of it — see the four different WhatsApp limits people mix up. If sending has stopped altogether rather than for individual recipients, that is a different problem: read what to do when a WhatsApp Business account is restricted.

What is the difference between WhatsApp errors 131049, 131047, 131048, 131026, 131050, 132015 and 130472?

These codes all surface as "the message did not arrive" and have almost nothing else in common. Meta's descriptions below are quoted from its Cloud API error code reference, checked on 22 August 2026.

The distinction that matters commercially is 131049 against 131048. One is a recipient you caught at a bad moment; the other is your number, and it gets worse until you change how you send.

Are you charged for a 131049, and what does it do to reporting?

You are not charged. Meta's pricing documentation states that "you are only charged when a template message is delivered", and a 131049 message was never delivered (Meta — WhatsApp Business Platform pricing). For the fuller picture of what does and does not reach Meta's bill, we cover what Meta charges for a message and what it doesn't separately.

In your own reporting it still lands as an attempted send that failed. What you need from a platform here is narrow: Meta's code kept per recipient, rather than one aggregate failure count that tells you nothing about which of the seven codes above you are looking at. WabaCRM stores the code, title and error text on each message row and filters and exports the message log on them — one of the duller entries in the feature list.

If one campaign shows a block of 131049s, check two things in order: whether the template was categorised as marketing when it did not need to be, and how recently that segment last replied to you. Between them they account for most of it.