Before you begin

Open the correct workspace and identify the affected sending number.
Find the campaign or conversation, template name, approximate time and provider reason.
Check existing evidence before sending another test. Obtain the recipient's permission for additional messages.

Do not reconnect a healthy sender or launch a duplicate campaign just because some recipients did not receive a message. First identify which part of sending failed.

Read the delivery states separately

State	What it tells you	What it does not establish
Pending, held or skipped before sending	WRKZY has not completed an outbound attempt for this recipient	That Meta rejected the message
Accepted by Meta	Meta returned a message identifier for the request	That the message was delivered
Sent	Meta reported that the message was sent	That the recipient's device received it
Delivered	Meta reported delivery	That the person read or replied to the message
Read or replied	A later engagement or response was recorded	Permission for every future marketing campaign
Failed or not delivered	An unsuccessful outcome was recorded	That an immediate retry will recover it

Meta can accept a request and return a failed status afterward. Keep recipients awaiting confirmation separate from confirmed failures. A quality assessment hold is also different from a failure; wait for a later status rather than creating duplicate sends.

Submission, delivery and engagement are separate events

01
LocalPrepared
Content and recipient are ready but nothing has left WRKZY.
02
PendingSubmitted
WRKZY handed the request to the connected provider.
03
AcceptedProvider accepted
The provider accepted processing, not necessarily delivery.
04
ResultDelivered or failed
A terminal provider event confirms delivery or an exception.
05
RecoverException reviewed
An owner diagnoses, recovers safely, or escalates with evidence.

Use the latest recorded provider evidence to distinguish a sending attempt from confirmed delivery and later engagement.

For example, six attempts may produce three delivered messages, two marketing delivery restrictions and one experiment restriction. The outcome is three delivered and three not delivered, even when none of the failed recipients is eligible for immediate retry. The retry count is not the failure count.

Find the affected recipients in WRKZY

Open Campaigns and select the WhatsApp campaign.
Review the campaign totals and Recipient Log. Filter by Failed to inspect the affected rows.
Read the recorded reason for each recipient. Do not infer a reason from a missing Delivered or Read status alone.
For an individual send, open the conversation in Inbox and inspect the failed message's status and provider reason.
For a broader pattern, open Settings → Message delivery → WhatsApp. Review sender health, quality, unavailable templates, recipient restrictions and recent campaign failures.

The same approved Marketing template remains a Marketing message when sent individually from Inbox. Sending it one person at a time does not change its category.

Error 131049: Meta marketing delivery restriction

Meta withheld the marketing message to protect recipient engagement. The provider may describe this as maintaining healthy ecosystem engagement. A green sender quality rating and an approved template do not guarantee delivery to every recipient.

What to do: Wait at least 24 hours before considering another appropriate marketing send. Recheck permission, relevance and recent contact frequency first. Meta does not expose the person's exact marketing allowance, and waiting does not guarantee that the next attempt will deliver. Avoid repeatedly resending the same message.

Error 130472: recipient in a Meta experiment

Meta withheld the Marketing template as part of a recipient messaging experiment. This is a provider delivery decision. WRKZY does not have a setting that removes a person from the experiment, and the code does not provide a guaranteed end time.

What to do: If the customer wants a response, contact them through an existing, consented alternative channel and ask them to message your business on WhatsApp first. Once their message arrives, reply to their enquiry within the 24-hour customer-service window. This creates a customer-initiated reply path; it does not permanently remove the experiment restriction or guarantee future Marketing template delivery.

Do not keep retrying the campaign to force delivery. Saving a contact, scanning a business card or completing a form in WRKZY does not itself open WhatsApp's customer-service window. The customer's WhatsApp message opens that window.

Error 131026: message undeliverable

Meta could not deliver the message. Possible causes include the number not being on WhatsApp, the recipient blocking the business, unaccepted WhatsApp terms or an outdated app. The code alone does not establish which cause applies.

What to do: Confirm the destination number and country code. Through an agreed alternative channel, ask the customer whether they can message the business, whether the business is blocked, and whether their app and terms are current. Correct the underlying issue before another attempt. Do not mark someone as having blocked you solely because this code appears.

Other failures and messages that were not attempted

Service window expired: Reply inside the customer's open service window, or select an appropriate approved template when the window is closed.
Template unavailable, paused or invalid: Check the selected sender, template approval, language, variables and required attachments. Sync or correct the template before another send.
Sender, permission or payment issue: Ask a workspace or Meta business administrator to review the recorded account error.
Skipped, suppressed or held before sending: Check the recorded consent, contact-data, frequency or approval reason. These recipients must remain distinct from messages that Meta accepted and later failed.
No recorded reason: Preserve the message or campaign ID and timestamp. Ask WRKZY Support to inspect the evidence rather than assuming a recipient restriction.

Why another platform or an earlier test may deliver

Compare the actual delivery evidence, not just a campaign labelled Sent. Check whether both attempts used the same sending number, business account, recipient number, exact template, category, language and comparable conversation conditions. Time and recent engagement can differ even when the contact list is identical.

A delivery from a different sending number does not isolate the platform as the cause. A failure from WRKZY does not, by itself, prove the application is at fault either. If comparable attempts behave differently, preserve both message identifiers and timestamps so the difference can be investigated. Use a small, consented test rather than resending an entire audience.

Retry only after reviewing the cause

WRKZY's failed-recipient recovery excludes known Meta restrictions such as 131049, 130472 and 131026 from immediate retry. A disabled retry action does not mean those failures disappeared, and it does not mean the recipient is permanently unreachable.

Use the supported recovery action only after correcting an eligible failure. Keep successful recipients out of the retry audience. Do not change promotional content to Utility merely to avoid a marketing restriction; templates must be used for their approved purpose.

What to give WRKZY Support

Provide the workspace, sender label, template name and language, message or campaign ID, send time and timezone, latest status and recorded Meta code. For a platform comparison, include the equivalent delivery evidence from the other attempt.

Redact customer details from screenshots and exports. Never include access tokens, app secrets or verification codes. See prepare safe support evidence.

Provider references

Provider rules and availability can change. The error descriptions explain the recorded decision; they are not a promise of delivery or a fixed recovery deadline.