WhatsApp Error 131049 (Healthy Ecosystem Engagement): Why Meta Held Your Message
Error 131049 means Meta held back a marketing message to protect the customer. It isn't charged. How to fix template categories and sending frequency.
In this guide
- Error 131049 means Meta chose not to deliver a marketing message, to protect a customer who is getting too many marketing messages. Your number and template are fine.
- Messages held back with 131049 are not charged.
- Retrying straight away doesn't help. Send marketing less often to the same people, and send it to people who are likely to read it.
- Order and booking updates sent as marketing templates are a common cause. Put transactional messages in the Utility category.
WhatsApp API error 131049 means Meta chose not to deliver a marketing template to a recipient to protect them from receiving too many marketing messages. It is not a block on your number, and Meta does not charge for the held-back message. Reduce repeat marketing, target people likely to read it, and use Utility templates for transactional updates.
What does WhatsApp error 131049 mean?
Error 131049 means Meta has held back a marketing template for that recipient. WhatsApp sorts every template into a category: marketing, utility or authentication. For marketing templates, Meta decides per recipient whether to deliver the message. If that person has received many marketing messages recently, or hasn't been reading them, Meta may hold yours back and return 131049.
| Question | Answer |
|---|---|
| Which messages get 131049? | Marketing templates |
| Is my number blocked? | No. Other messages to other people keep going out |
| Am I charged? | No. Held-back messages aren't billed |
| Will retrying work? | Not straight away. The same person is likely to be held back again |
The decision is about the recipient, not about you. That's why one campaign can have a 131049 rate that looks random: the customers who are held back are usually the ones getting many marketing messages from other brands as well.
What won't fix error 131049?
Quick workarounds do not change Meta's per-recipient decision about delivering a marketing message.
- Resending the same message within hours. Meta's view of that customer hasn't changed, so the resend is likely to be held back too.
- Creating a new template with the same content. The category is what matters, not the template name.
- Switching to free-form text. Outside the 24-hour window, free-form messages fail with error 131047 instead.
- Unofficial tools. Getting around Meta's rules puts your number at risk of being restricted.
How can I reduce error 131049?
Reduce 131049 by correcting transactional template categories, spacing out marketing, and targeting people likely to read it.
- Check the category of your transactional templates. Order confirmations, shipping updates, COD confirmations and booking messages should be Utility templates. If one was approved as Marketing, it can be held back like a promotion. Rewrite it without offers or promotional wording and submit it as Utility.
- Send marketing less often to the same people. If you send a campaign every day to your full list, the most active customers hit the limit first. Space campaigns out and rotate segments.
- Target people who read your messages. Send to recent buyers, recent cart abandoners and customers who replied in the last few months, rather than your whole contact list.
- Make each message worth opening. One clear offer, a product image and a single button do better than a long text with several links.
- Retry later, not now. If a held-back message matters, send it to that customer again in a later campaign, days later, not hours.
How many 131049 errors are normal?
Some held-back messages on large campaigns are normal, especially when your list includes people who shop with many brands. What should worry you is a rising share week after week, or 131049 on order updates. The first means your sending is too frequent for your list; the second means a transactional template is in the wrong category.
How can I track 131049 in WALoops?
In WALoops, the WhatsApp page's health card counts messages Meta held back in the last 7 days, shown as "Held back by Meta". The same card lists the most common send errors from the last 7 days, your quality rating and your message limit, so you can see whether 131049 is the main problem or one of several.
In broadcast campaigns, segment by tags or recent activity so each campaign goes to the people most likely to read it. WALoops adds no markup on Meta's fees; the WhatsApp API pricing guide lists what each category costs in India.
Meta also offers a Marketing Messages API for marketing templates. If you still see many 131049 errors after fixing categories and frequency, our team can send you the link to opt in from your own Meta Business account.
Which WhatsApp errors are related?
Related WhatsApp API errors include 131047 for free-form messages outside the 24-hour window and 131026 for undeliverable messages.
| Code | What it means |
|---|---|
| 131049 | Marketing message held back to protect the customer. Not charged. |
| 131047 | Free-form message outside the 24-hour window. Send a template. |
| 131026 | Message undeliverable, usually because the number isn't on WhatsApp. See the 131026 guide. |