WhatsApp API message not delivered: the causes, in order
An accepted WhatsApp API message is not a delivered one: Meta reports the outcome later in a status webhook, sent, delivered, read or failed, with an error code. Check in order: the failed status and its code, the 24-hour window (131047), the payment method (131042), the template (132001, 132015), the recipient (131026, 131049, 131050), then the number's limits and connection.
easyCoexistence watches every connected number around the clock, emails you when Meta stops delivering, drops the link or lowers quality, and forwards Meta's status webhooks unchanged to your system.
sent (one check mark), delivered (two), read (two blue) and failed (a red error triangle), as status webhooks report them.
More than 24 hours have passed since the recipient last replied; Meta says to send a template instead.
Unable to deliver: the number is not on WhatsApp, the recipient has not accepted the new terms, or runs an old WhatsApp version.
Default time WhatsApp retries an undelivered utility or marketing template before dropping it; authentication templates default to 10 minutes.
Fixed throughput of a number used in both the WhatsApp Business app and the Cloud API.
Why does an accepted message still not arrive?
Because the API answer and delivery are two separate events. When you send, Meta returns a message id as soon as it accepts the request; whether the message reaches the customer's phone comes later, in a status webhook on the messages field. sent means it left Meta's servers (one check mark), delivered that it reached the device (two), read that it was opened (two blue), and failed that it could not be sent or delivered, shown to you with an errors array: code, title and error_data.details. So the first move is never to guess: find the failed status for that message id and read its code. If you have no webhook destination, nothing records it.
What are the causes, in the order to check them?
From the most common on a newly connected number to the rarest. Each line names Meta's code, so the failed status tells you which one you are in:
- Window closed: 131047, more than 24 hours since the customer last wrote. Free-form messages need an open window; send a template.
- Payment: 131042, or templates silently dropped. Since 1 October 2026 service messages also stop once 1,000 a month are used without a payment method.
- Template: 132001 not approved or wrong language, 132000 wrong number of variables, 132012 wrong format, 132015 paused, 132016 disabled.
- Recipient: 131026 not on WhatsApp, old version or terms not accepted; 131050 stopped marketing messages; 131049 held back for healthy engagement; marketing templates to US numbers are not delivered.
- Limits: 131048 restricted after spam signals, 131056 too many messages to one person, 130429 throughput, 20 messages per second on a Coexistence number.
- Account: 131031 or 368, the WhatsApp Business Account restricted or disabled for a policy violation.
- Connection: the number is no longer linked, for example after 14 days without opening the WhatsApp Business app.
How do you handle the recipient-side codes?
Differently, because some deserve a retry and some never do. 131050 means the person chose to stop marketing messages from you: Meta says not to retry, and the user_preferences webhook tells you when they stop or resume. 131049 is Meta holding a marketing message back to keep engagement healthy, often a per-user limit on marketing templates: Meta advises waiting at least 24 hours before resending, since resending sooner only returns the same error. 131026 covers numbers that are not on WhatsApp, users who have not accepted WhatsApp's current terms and very old app versions; check the number's format and country code first, then ask the customer through another channel.
How long does WhatsApp keep trying to deliver?
For the message's time to live. When a phone is off or out of coverage, WhatsApp retries delivery instead of failing at once: by default for 30 days on utility and marketing templates and 10 minutes on authentication templates. A business can shorten it per template with message_send_ttl_seconds, from 30 seconds to 12 hours for utility and 30 seconds to 15 minutes for authentication. A message that cannot be delivered within its TTL is dropped. So a message with a sent status and no delivered status after hours is usually waiting on the customer's phone, not lost; set a short TTL on codes and time-sensitive alerts so a late delivery never confuses anyone.
What does this mean for AI replies and automations?
Read the run first, then the status. In the Runs tab, a Skipped run sent nothing and says why: "More than 24 hours since the customer's last message", "You answered this chat from your phone recently" or "AI reply limit for this chat reached this hour". A Done run means Meta accepted every reply, which is not proof of delivery. easyCoexistence does not store message statuses: with automations on, they reach your forward URL if you set one, and in direct mode they go straight to your own endpoint. From ChatGPT or Claude, ask your AI to run get_number_health: it returns the live status, quality rating and the last 15 monitoring events, including a sending block with Meta's code.
How to set it up
- Find the statusLook up the message id in your webhook log and read the latest status: delivered, read, sent only, or failed with an error code.
- Match the codeLook up the failed status's code in the list of causes above and in Meta's error codes reference.
- Check the accountConfirm the WhatsApp Business Account has a default payment method, a currency and a time zone in Billing & payments.
- Check the templateIf it was a template, confirm it is APPROVED in that language and the variables match its definition.
- Check the numberAsk your AI to run get_number_health, or open the number in the dashboard, to see the connection and any sending block.
Common mistakes
- Retrying on a 131050. The person stopped marketing messages from you; more attempts are never delivered and can only add negative signals.
- Reading a message id as delivered. Meta accepts first and reports failures later, so a workflow that stops at the id misses every refused message.
- Sending a free-form reply a day later. After 24 hours without a customer message only a template is accepted.
- Running without a webhook destination. Failed statuses arrive only as webhooks, so without one the reason a message did not arrive is lost.
Your AI can check a number from ChatGPT or Claude with get_number_health. US$ 9 down to US$ 0.75 per number per month, falling as you add numbers, with the first 3 days free.
easyCoexistence is a multichannel API and MCP server that connects AI agents such as Claude and ChatGPT to WhatsApp, Instagram, TikTok, Facebook and more. On WhatsApp it uses Coexistence: the business keeps using its number in the WhatsApp Business app while the AI works through Meta's official API.
Frequently asked questions
Why did the message show one check mark for hours?
One check mark is the sent status: Meta sent it, but the phone has not received it, usually because it is off or offline. WhatsApp keeps retrying until the template's time to live runs out, 30 days by default for utility and marketing.
Why do replies arrive but templates do not?
Usually a payment method problem on the WhatsApp Business Account. Meta delivers service messages within the number's monthly free tier without one, but does not deliver templates. Add a card in Billing & payments.
Can I see failed messages in the WhatsApp Business app?
Not reliably. On a Coexistence number, messages sent through the API appear in the app's chat thread, but the reason a message failed comes only in the status webhook's error code.
Does Meta charge for messages that were not delivered?
No. Meta charges only for delivered messages, and attempts with a paused template are not charged either.
Keep reading
Ready to get started?
Set up WhatsApp Coexistence in minutes, not months. The app keeps working on the phone.
Start Free TrialVerified on