# 🚫 Error: This message was not delivered to maintain healthy ecosystem engagement

<figure><img src="/files/Luwcq6L7D424lerZpNq9" alt=""><figcaption></figcaption></figure>

This is not a QuickReply.ai failure — the message was **intentionally blocked by WhatsApp (Meta)**.

### ❓What Does This Error Mean?

This error appears when WhatsApp prevents delivery of a Marketing Template to a specific user.\
Meta applies **per-user limits** to avoid excessive marketing or spam-like frequency for an individual recipient.

When these limits are reached — **even if the template is valid and the number is active** — WhatsApp may decide **not to deliver the message**.

### 🔍 Why This Error Happens — As per Meta

The official Meta error code related to this is:

<table><thead><tr><th width="178.3828125">Error Code</th><th>Description from Meta</th><th>Reason</th></tr></thead><tbody><tr><td>131049</td><td><em>Meta chose not to deliver.</em></td><td><em>This message was not delivered to maintain healthy ecosystem engagement.</em></td></tr></tbody></table>

Meta enforces **Per-User Marketing Template Message Limits** based on multiple factors, including but not limited to:

{% hint style="info" %}
See Meta’s official documentation on **Per-User Marketing Template Message Limits** here 👇\
<https://developers.facebook.com/documentation/business-messaging/whatsapp/templates/marketing-templates/per-user-limits>
{% endhint %}

| Reason WhatsApp Blocks the Message                         | Explanation                                                                   |
| ---------------------------------------------------------- | ----------------------------------------------------------------------------- |
| Too many marketing messages sent recently to the same user | WhatsApp avoids overwhelming users and promotes positive messaging engagement |
| User has not interacted with previous marketing messages   | Meta reduces reach for uninterested recipients                                |
| Low-quality or repetitive marketing messaging patterns     | Templates perceived as overly promotional or frequent may be blocked          |
| Sudden spike in campaigns to the same recipients           | Risk-control logic triggers ecosystem-protection rules                        |

These rules apply **even if the user is active on WhatsApp**, **even if the template is approved**, and **even if prior messages were delivered successfully**.

***

### 🛠️ How to Fix It

This error **cannot be fixed instantly** because the delivery decision is made by WhatsApp (Meta), not QuickReply.ai.

Recommended steps:

* Wait at least 24 hours before attempting to send the template again.\
  Sending immediately again will likely result in the same error.
* Avoid sending frequent marketing messages to the same contact in short intervals
* Use conversational templates occasionally to encourage replies and restore positive engagement
* Segment high-intent users separately (e.g., cart abandoners, repeat buyers) for better delivery probability

{% hint style="success" %}
If you believe the issue is due to messaging fatigue, redesign your flow to follow a healthier contact cadence — WhatsApp rewards engagement.
{% endhint %}

***

### 🔔 Final Note

This rejection is **controlled entirely by WhatsApp for user-protection reasons**. QuickReply.ai successfully triggered the message, but **Meta decided not to deliver it** based on per-user engagement limits.

Once the recipient becomes more engaged or enough time has passed, message delivery should resume normally.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.quickreply.ai/overview/messaging-channels/whatsapp/errors/error-this-message-was-not-delivered-to-maintain-healthy-ecosystem-engagement.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.