> ## Documentation Index > Fetch the complete documentation index at: https://docs.ycloud.com/llms.txt > Use this file to discover all available pages before exploring further. # Quality and delivery controls > Understand why approved messages can be delayed or blocked, and respond to quality signals without blind retries. A valid API request and an approved template do not guarantee that every message will reach its recipient. WhatsApp uses quality signals and delivery controls to protect customers from unwanted messages. Diagnose the affected level before changing a template, increasing spend, or retrying a campaign. ## Controls that can affect delivery **Pacing** allows WhatsApp to evaluate responses to a template before releasing more messages. Do not interpret every delay as a transport failure. **Pausing or disabling** can make a template unavailable after negative feedback or poor engagement. Check the current template status before scheduling additional sends. **Recipient-level marketing limits** can prevent a customer from receiving another marketing message even when your own portfolio has capacity. These limits concern the customer's overall experience, not only messages from your business. Meta describes these mechanisms in [template fundamentals](https://developers.facebook.com/docs/whatsapp/business-management-api/message-templates/). Their thresholds and availability can change; do not promise a fixed quota for each customer. ## Diagnose from the result | Observation | First action | | - | - | | Request accepted but no delivery yet | Follow status updates and check for pending processing; do not immediately duplicate the send. | | Template is paused or disabled | Stop dependent sends and review feedback and content. | | Failures cluster around one template | Review its category, quality, status, and recent audience. | | Failures cluster around individual customers | Examine recipient-specific errors and communication preferences. | | Failures affect many templates and numbers | Check portfolio capacity, account status, integration health, and billing. | Use [Message delivery statuses](/en/documentation/whatsapp-business-platform/messaging/message-delivery-statuses) for the lifecycle of one message. Preserve the exact error code and relevant identifiers when contacting support. ## Common error codes and the next check YCloud can return its own errors and upstream WhatsApp errors. Preserve the actual code and details; the following are common **Meta** codes, not every possible YCloud result. | Code | What to check | | - | - | | `130429` | Throughput exceeded; slow dispatch. | | `131026` | Undeliverable; do not conclude the recipient blocked you. | | `131042` | Billing or payment setup; not automatically a policy ban. | | `131047` | Service window expired; choose an appropriate approved template. | | `131049` | Recipient/engagement delivery control; avoid immediate retries. | | `131050` | The recipient stopped marketing from your business; do not retry that marketing send. | | `132000` | Template parameter count mismatch. | | `132001` | Template name, language, or approval mismatch. | | `132015` / `132016` | Template paused or disabled; stop dependent sends. | For `131049`, Meta advises waiting at least 24 hours before a possible resend when a recipient limit is suspected. Waiting does **not** guarantee delivery; first confirm consent, relevance, and whether another attempt is justified. This is different from `131050`, which says the recipient opted out of marketing. Source: [Meta error codes](https://developers.facebook.com/documentation/business-messaging/whatsapp/support/error-codes). ## Run a focused diagnosis Compare a small set of representative messages by template, sender, audience source, time, and error. Do not test by repeatedly contacting the same failing recipient. For example, if one template fails across several numbers while other templates work, investigate that template's status and parameters first. If many templates fail after a billing change, examine billing and account setup before rewriting their copy. Create a short incident record: observed failure, affected scope, last known successful send, recent changes, containment action, and next owner. This turns “WhatsApp is not working” into a specific, testable problem. ## Improve the customer experience Start with relevance before volume: * Send what the customer expected when opting in. * Use recent customer intent and a clear reason to contact them. * Coordinate frequency across campaigns and automations. * Identify your business clearly. * Keep content accurate, useful, and easy to act on. * Make opting out straightforward and apply it promptly. Monitor both delivery outcomes and customer responses. A high delivery rate with growing opt-outs is not a healthy campaign. ## Retry deliberately Retry only when the error indicates a recoverable condition and the message is still useful. Use bounded retries and avoid creating duplicate customer notifications. Do not repeatedly resend a blocked marketing message, rotate business numbers, or relabel promotional content as utility to bypass controls. If the customer initiates a new conversation, respond to their actual request using the permitted message type. Do not treat that interaction as permission to restart unrelated campaigns. ## Related topics * [Template review and lifecycle](/en/documentation/whatsapp-business-platform/messaging/message-templates/template-review-and-lifecycle) * [Messaging limits and throughput](/en/documentation/whatsapp-business-platform/pricing-limits-and-quality/messaging-limits-and-throughput) * [Customer opt-out](/en/documentation/whatsapp-business-platform/consent-policies-and-account-health/customer-opt-out) * [Account restrictions and appeals](/en/documentation/whatsapp-business-platform/consent-policies-and-account-health/account-restrictions-and-appeals) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.