> ## Documentation Index > Fetch the complete documentation index at: https://docs.nova.galaxa.in/llms.txt > Use this file to discover all available pages before exploring further. # Mastering Smart Retry & Meta Frequency Limits > How to maximize WhatsApp deliverability, recover lost revenue via rolling backoff windows, and safeguard customer trust with automated inbound support conflict cancellation. # Mastering Smart Retry & Meta Frequency Limits In high-volume e-commerce marketing, deliverability directly dictates your campaign ROI. However, Meta imposes strict per-user frequency limits on marketing conversations to protect WhatsApp users from spam. When a customer has received marketing messages across multiple businesses within a short timeframe, Meta rejects additional promotional templates with **Error Code `131049`** (Meta Frequency Limit) or **Error Code `130429`** (Throughput Rate Limit). Understanding how to navigate Meta's frequency caps separates amateur marketing setups from high-converting enterprise growth engines. *** ## Why Traditional Broadcast Tools Fail Most legacy marketing platforms handle WhatsApp delivery errors in one of two flawed ways: 1. **Immediate Resend (The Spam Trap)**: Re-blasting failed messages immediately. Because Meta's frequency limit on the user's handset operates on a 24-hour rolling window, immediate resends fail repeatedly. This wastes API quota, irritates customers, and rapidly downgrades your WhatsApp Business Account (WABA) Quality Rating from **Green** to **Red**. 2. **Ignored Failures (The Revenue Leak)**: Dropping failed messages completely while marking them as "Sent" in the dashboard. This hides delivery issues, skews analytics, and leaves 15–25% of potential campaign GMV unrecovered. *** ## The Nova Smart Retry Solution Nova Core incorporates an autonomous, frequency-aware retry engine engineered specifically around Meta's 24-hour marketing cooldown windows: ```mermaid theme={null} flowchart TD A[Broadcast Campaign Dispatched] --> B{Meta Delivery Result} B -->|Delivered| C[Delivered & Read Receipts] B -->|Code 131026: Not on WhatsApp| D[Permanent Suppression: Excluded from Denominator] B -->|Code 131049 / 130429: Frequency Cap| E[Enqueued in Rolling Smart Retry Queue] E --> F{Rolling Cooldown Schedule} F -->|+12h Window| G[Attempt 1: Automated Retry] G -->|Delivered| H[Reconciled to Campaign Telemetry] G -->|Still Capped| I[Attempt 2: +24h Window] I -->|Delivered| H I -->|Still Capped| J[Attempt 3: +48h Final Window] J -->|Delivered| H J -->|Exceeded Cap| K[Hard Stop: 3 Attempts Max] L[Customer Sends Inbound Support Message] -->|Instant Trigger| M[Purge All Pending Marketing Retries] ``` *** ## 1. Rolling Backoff Schedule (+12h, +24h, +48h) When Meta returns a transient `131049` or `130429` error, Nova Core places the recipient into an intelligent, delayed work queue: * **Attempt 1 (+12 Hours)**: Dispatched 12 hours after the initial failure, when many user frequency buckets reset. * **Attempt 2 (+24 Hours)**: Dispatched 24 hours after Attempt 1 if the handset remains capped. * **Attempt 3 (+48 Hours)**: Dispatched 48 hours after Attempt 2 as a final recovery window. * **Hard Attempt Cap (3 Max)**: If the message cannot be delivered after 3 attempts, it is permanently closed to prevent message fatigue. * **Randomized Jitter ($\pm 15$ min)**: A randomized time offset is applied to prevent thundering herd spikes on Meta's network. *** ## 2. Inbound Support Conflict Cancellation Sending a marketing coupon to a customer who just reached out to your support team asking *"Where is my order?"* or *"My item arrived damaged"* damages your brand reputation. Nova Core's webhook listener continuously monitors incoming messages: * If any customer with a pending retry initiates an inbound support conversation, Nova Core **immediately purges all scheduled promotional retries** for that phone number. * The retry record is marked as `status: "cancelled_inbound"`. * This ensures promotional marketing never collides with active customer service conversations. *** ## 3. Permanent Suppression vs. Transient Recovery Nova Core strictly separates transient errors from permanent failures: | Meta Error Code | Category | Classification | Smart Retry Action | | :- | :- | :- | :- | | **`131049`** | `meta_frequency_limit` | **Transient (Recoverable)** | Enqueued in rolling backoff (+12h, +24h, +48h) | | **`130429`** | `throughput_rate_limit` | **Transient (Recoverable)** | Enqueued for Cloud API rate-limit backoff | | **`131026`** | `not_on_whatsapp` | **Permanent (Suppressed)** | Never retried; excluded from effective denominator | | **`131048`** | `spam_rate_limit` | **Permanent (Suppressed)** | Suppressed immediately to safeguard WABA quality | | **`131050`** | `marketing_opt_out` | **Permanent (Suppressed)** | Excluded from all current and future marketing | *** ## 4. Honest Denominator Accounting Many marketing platforms claim "99% delivery rates" by including non-existent numbers in vanity calculations. Galaxa Nova AI enforces honest, mathematically sound denominator accounting: $\text{Effective Recipient Base} = \text{Sent} - \text{Not-on-WhatsApp [Code 131026]}$ $\text{Honest Delivery Rate} = \left(\frac{\text{Delivered}}{\text{Effective Recipient Base}}\right) \times 100$ * **Not-on-WhatsApp (`131026`)**: These numbers cannot physically receive WhatsApp messages. Deducting them from the denominator gives merchants an accurate benchmark of true reachable reach. * **Frequency Limits (`131049`)**: These are valid, high-value WhatsApp users who are temporarily capped. They remain in the denominator and are recovered through Smart Retry. *** ## 5. Reconciled Telemetry & Zero Double-Billing When a message is successfully delivered via Smart Retry: * **Campaign Dashboard Updates Dynamically**: The `Delivered` count and `Delivered by Retry` chip increment automatically. * **Zero Double-Billing**: You only pay the wholesale Meta conversation fee once upon successful delivery. Nova Core never charges duplicate campaign fees. * **72-Hour Attribution Extension**: The 72-hour revenue attribution window begins from the moment the message was actually delivered, ensuring accurate ROAS tracking. *** ## Merchant Checklist for High Deliverability > **Enable Smart Retry** > > Keep Smart Retry toggled ON in your campaign composer. It automatically recovers 15–25% in blocked reach without manual intervention. > **Monitor WABA Quality** > > Check your WhatsApp Business Account quality rating in the dashboard. Keep it in the **Green zone** by targeting engaged customer segments. > **Include Easy Opt-Outs** > > Provide a quick-reply button (e.g. "Reply STOP to unsubscribe"). Nova Core automatically suppresses opted-out contacts across all future broadcasts. > **Schedule for Peak Hours** > > Dispatch campaigns between 10:00 AM and 8:00 PM IST. Avoid late-night dispatches that trigger high opt-out rates. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.