WhatsApp message not delivered: causes and fixes (2026)

Most teams use WhatsApp for the messages that matter most: appointment reminders, order updates and campaigns.

Then a reminder goes missing. Your broadcast report shows a block of failed sends. One customer says they never got their update.

A failed status on its own only tells you something went wrong. Without the reason, your team guesses and resends, and the customer still misses the message.

Resending can make it worse. Meta caps how many marketing templates each person receives, and it warns that early retries can trigger a longer block.

On the WhatsApp Business API, a failed message usually comes back with a numbered error code that names the cause and points to the fix.

In this guide, you'll learn 6 common causes, what each code means, and how to fix and prevent each one.

How do you know a WhatsApp message wasn't delivered?

Check the message status. On the WhatsApp Business API, every message goes through sent, delivered and read, or stops at failed. Failed means it won't arrive, and the error code attached to it tells you why.

Sent means the message reached WhatsApp's servers but not the phone yet. Delivered means it's on the customer's device.

These are the statuses SleekFlow shows, as described in its Help Center.

Sent but not delivered isn't a failure. It often means the customer's phone is off or offline. WhatsApp's own help page says a message sitting on a single check mark is normal.

Where to find the error

The error is on the failed message itself. Where you look depends on how you sent it:

• One-to-one chats. In SleekFlow's inbox, hover over the failed icon to see the error and how to fix it.
• Broadcasts. Open the broadcast's History tab. Filter recipients by delivery status to see who failed, and check the remarks column. You can export the list as a CSV.

Why isn't my WhatsApp Business message delivered?

There are 6 common causes behind failed WhatsApp Business messages: the 24-hour reply window closed, the customer can't receive messages, the customer opted out or hit a marketing limit, you sent too much too fast, the template has a problem, or the account is blocked. Each one has its own Meta error code and its own fix.

Source: Meta's WhatsApp error codes page.

1. The 24-hour window closed (131047)

When a customer messages you, you have 24 hours to reply with any message you like. After that, WhatsApp only lets you send a pre-approved template. A free-text follow-up sent on day two fails with 131047.

The fix is a template that gives the customer a reason to reply, which opens a new window.

2. The customer can't receive it (131026)

This is the catch-all "undeliverable" code. Meta lists three common reasons:

• Not on WhatsApp. The number isn't a WhatsApp number.
• Terms not accepted. The customer hasn't accepted WhatsApp's latest terms of service and privacy policy.
• Old app. The customer is on a very old version of WhatsApp.

You can't fix these from your side. Reach the customer another way, such as email or SMS, and ask them to check.

3. The customer opted out or hit a marketing limit (131050, 131049)

Customers can stop marketing messages from your business inside WhatsApp. When they do, your marketing templates fail with 131050. Don't keep sending to them.

Meta also caps how many marketing templates each person gets from all businesses. The cap moves with how engaged that person is. Hit it and you get 131049.

Resending too soon makes it worse. Meta's per-user limits page says to wait at least 24 hours, because early retries can trigger a temporary block for those customers.

The same page says WhatsApp doesn't currently deliver marketing templates to people with US phone numbers.

4. You sent too much, too fast (130429, 131048, 131056)

Four limits can stop a send:

• Speed (130429). Your setup hit the maximum number of messages the API will take at once.
• Spam rate limit (131048). Meta has restricted how many messages this number can send. Its advice is to check your quality status in WhatsApp Manager.
• One person (131056). Too many messages to the same customer in a short time.
• Daily messaging limit. WhatsApp caps how many people you can start conversations with in a rolling 24-hour period, shared by every number in your business portfolio. Meta's messaging limits page explains the tiers.

For big sends, split the audience into batches that fit your daily limit.

5. The template has a problem (132000, 132001, 132015, 132016)

Template errors are usually set-up mistakes: a template that isn't approved yet, a wrong language code, or a missing variable such as a first name.

Paused and disabled templates are different. Meta pauses a template for low quality, and disables it if that keeps happening. Rewrite it so it's more useful to the people who get it.

6. The account is blocked (131031, 368, 130497, 131042)

These stop every message, not just one. A restricted or disabled account (131031 or 368) means Meta found a policy breach. Our guide to a banned WhatsApp Business account covers what to do.

The other two are simpler. 130497 means your business category isn't allowed to message some countries. 131042 means a billing problem on your WhatsApp Business account.

How do you stop WhatsApp Business messages failing?

You stop most failures before you hit send. Get clear opt-in, reply inside the 24-hour window, check templates before a big campaign, and keep sends within your daily limit. After a send, clean out numbers that failed for good, and give marketing limits at least 24 hours before you try the same customer again.

• Get opt-in first. Only message people who agreed to hear from you. See how to collect WhatsApp opt-ins.
• Reply inside 24 hours. Use a template once the window has closed.
• Test templates before a campaign. Check approval, language and every variable on a small send first.
• Batch large sends. Keep each batch within your daily messaging limit.
• Clean your list. Remove numbers that failed with 131026 or 131050 instead of retrying them.
• Wait out marketing limits. Leave at least 24 hours before resending a template that failed with 131049.
• Watch your quality rating. It affects how far your limits can grow. Our WhatsApp broadcast guide covers how it works.

How SleekFlow helps you find and fix failed messages

SleekFlow shows the reason for each failed message, right where your team already works.

• In the inbox. Hover over a failed message to see the error and the suggested fix.
• In broadcasts. The History tab counts sent, delivered, read, replied and failed. Filter by failed, then add those customers to a list for follow-up or export them as a CSV.
• In channel settings. You can see your business portfolio's messaging limit before planning a big send.
• In the Help Center. The WhatsApp troubleshooting guide lists every error code with its fix.

How alfred24 made its WhatsApp delivery updates reliable

alfred24 is a Hong Kong logistics company that runs smart lockers and pickup points. Its first WhatsApp provider wasn't an official one. Messages went out of sync, and reconnecting after a phone crash could take up to three hours.

It moved to SleekFlow and also shifted delivery updates off SMS, where some messages failed to send. According to the story, the team can now make sure updates reach customers and see whether they've been read.

Results:

• 60% decrease in response time
• 80% decrease in manpower
• 300% increase in open rate

Read the full case study

What to do when a WhatsApp message fails

A failed WhatsApp message usually comes back with an error code, and the code points to the fix: send a template, wait out a limit, or take a number off your list.

The bigger risk is not seeing failures at all, so a follow-up or a campaign misses customers and nobody notices. Book a demo to see how SleekFlow shows the reason for every failed message in your inbox and broadcast reports.