হোয়াটসঅ্যাপ ত্রুটি

Shown in the dashboard as: Not on WhatsApp

What It Means

WhatsApp says this phone number does not have a WhatsApp account, so the message cannot be delivered.

Common Causes

• The person does not use WhatsApp on this number
• A typo in the saved number
• The number is saved without its country code and points to someone else

How to Fix

1. 1.Check the number in Contacts & CRM > All Contacts and correct it if needed
2. 2.BeeCastly adds the tag "undeliverable" to this contact. Future broadcasts skip contacts with that tag, so remove the tag after you fix the number
3. 3.In Messages > WhatsApp you can use "Invite to WhatsApp" under the failed message to text the person instead

Shown in the dashboard as: Not on WhatsApp

What It Means

Meta could not deliver the message. The number may not be on WhatsApp, or it cannot receive messages from businesses.

Common Causes

• The number is not on WhatsApp
• The number cannot receive messages from businesses

How to Fix

1. 1.Check the number with the person
2. 2.The contact gets the "undeliverable" tag, so remove it in Contacts & CRM > All Contacts if you want to try again later

What It Means

The saved phone number has no country code, and BeeCastly could not work out which country it belongs to.

Common Causes

• The number was imported or typed without the + and country code
• The contact has no country set
• On the Cloud API, Meta may report a badly formatted number as code 131009

How to Fix

1. 1.Open the contact in Contacts & CRM > All Contacts
2. 2.Save the number in international format: a + sign, the country code, then the number
3. 3.Send the message again

What It Means

WhatsApp refused the message because it was blocked.

Common Causes

• The person blocked your WhatsApp number
• On the Cloud API: Meta limited your number because too many people blocked or reported your messages (Meta code 131048)

How to Fix

1. 1.Respect the block and do not keep messaging this person. The contact gets the "undeliverable" tag
2. 2.If many messages fail like this, send only to people who opted in and pause promotional messages for a while

What It Means

BeeCastly stopped the message on purpose, just before sending. The error text tells you which rule stopped it.

Common Causes

• Contact has unsubscribed
• The contact is marked unsubscribed or bounced
• Contact is tagged "unsubscribed", "undeliverable" or "do-not-contact"
• The number is on your Do Not Call list
• The contact was deleted after the broadcast started
• Sending was paused for your account, or it was quiet hours, and the message waited too many times

How to Fix

1. 1.Usually nothing to fix: the rule is protecting the contact and your number
2. 2.If a tag is wrong, remove it in Contacts & CRM > All Contacts
3. 3.If the number should not be on the Do Not Call list, remove it in AI Voice Calls > Do Not Call
4. 4.Then retry the message

Shown in the dashboard as: Session expired

What It Means

BeeCastly could not reach your WhatsApp connection when it tried to send.

Common Causes

• QR connection: your phone logged out the linked device, or the connection dropped
• Either connection: many sends in a row failed, so BeeCastly paused sending for a short time and kept retrying

How to Fix

1. 1.Go to Integrations > Channels > WhatsApp and check the status
2. 2.If it is not connected, reconnect it (scan the QR code again for a QR connection)
3. 3.Then retry. A broadcast will not retry while WhatsApp is disconnected

What It Means

The message left BeeCastly, but WhatsApp never confirmed it. BeeCastly marks it Failed after about two minutes so you do not think it was delivered.

Common Causes

• WhatsApp has restricted your linked device, for example "You can't start new chats right now"
• The connection dropped right after sending

How to Fix

1. 1.Open WhatsApp on your phone and check Linked devices for a warning
2. 2.Use "Reconnect WhatsApp" under the failed message, or go to Integrations > Channels > WhatsApp
3. 3.Wait for any restriction to end, then resend

Shown in the dashboard as: Rate limited

What It Means

Messages were going out faster than allowed, so the send was held back.

Common Causes

• Your account is sending many messages at once, for example during a large broadcast
• Cloud API: Meta's send-rate limit for your number (Meta codes 80007, 130429)
• Cloud API: too many messages to the same person in a short time (Meta code 131056)

How to Fix

1. 1.Nothing is lost. BeeCastly waits and retries by itself
2. 2.If messages still end as Failed, retry them later from the broadcast
3. 3.Spread big sends out over time

What It Means

WhatsApp did not answer in time, so BeeCastly gave up on that try.

Common Causes

• A slow or unstable connection to WhatsApp or Meta
• A short outage on WhatsApp's side

How to Fix

1. 1.BeeCastly retries by itself
2. 2.If it still fails, check your WhatsApp connection and retry

Shown in the dashboard as: Re-engagement required

What It Means

On the Cloud API you can send a normal message only within 24 hours of the customer's last message to you. After that, Meta only allows an approved template.

Common Causes

• The customer has not messaged you in the last 24 hours
• The broadcast sent plain text instead of a template

How to Fix

1. 1.Send an approved template instead (Campaigns > Templates)
2. 2.When the customer replies, you can send normal messages again for 24 hours

What It Means

The broadcast uses a WhatsApp template that Meta has not approved, so it cannot be sent.

Common Causes

• The template is still Pending review
• Meta rejected the template
• Meta itself may report this as code 132001: the template does not exist, or not in the language you picked

How to Fix

1. 1.Open Campaigns > Templates and check the template's status
2. 2.Wait for it to show Approved, or fix and resubmit a rejected one
3. 3.Then retry the broadcast

Shown in the dashboard as: Template param error

What It Means

The template was sent with a different number of variables than Meta expects.

Common Causes

• The template was changed after the broadcast was set up
• A variable in the template has no value for this contact

How to Fix

1. 1.Check the template in Campaigns > Templates
2. 2.Make sure every variable gets a value, then send again

What It Means

Your Meta WhatsApp account is still in test mode, and this number is not on its list of allowed recipients.

Common Causes

• Your Meta app has not finished review yet, so it can only message a few test numbers

How to Fix

1. 1.In WhatsApp Manager (business.facebook.com), open Phone Numbers and add the number as a recipient
2. 2.Finish Meta's review to message everyone

What It Means

Your number has started as many new conversations today as Meta allows for its messaging tier.

Common Causes

• A big broadcast to people who have not messaged you recently

How to Fix

1. 1.Wait for the 24-hour period to roll over, then retry
2. 2.Meta raises your limit as your number builds a good sending history

What It Means

Meta has temporarily restricted your WhatsApp account, usually for a policy problem.

Common Causes

• Messages that broke WhatsApp's business rules
• Many people blocking or reporting your messages

How to Fix

1. 1.Open Account Quality in Meta Business (business.facebook.com) to see the reason
2. 2.Request a review there if you think it is a mistake

What It Means

Your own WhatsApp number is not registered for sending on the Cloud API yet. This is not a problem with the contact.

Common Causes

• Number registration in Meta was not finished
• The number was moved or re-added in Meta

How to Fix

1. 1.In WhatsApp Manager (business.facebook.com), open your number and finish verification and registration
2. 2.Test the connection again in Integrations > Channels > WhatsApp
3. 3.Then retry. Your contacts are not tagged for this error

What It Means

Meta is still reviewing your WhatsApp number, or its display name is not approved yet, so it cannot send.

Common Causes

• A newly added number
• The display name is pending, declined or expired

How to Fix

1. 1.In WhatsApp Manager (business.facebook.com), open Phone Numbers and check the number's status and name
2. 2.Submit the display name for review if needed, and retry once Meta approves it

What It Means

The broadcast was set to send through the Cloud API, but your account has no Cloud API details saved.

Common Causes

• The Cloud API was never connected, or it was disconnected after the broadcast was created

How to Fix

1. 1.Connect the Cloud API in Integrations > Channels > WhatsApp
2. 2.Then retry the broadcast

What It Means

Meta's servers returned an error without a reason code.

Common Causes

• A temporary problem on Meta's side

How to Fix

1. 1.BeeCastly retries by itself
2. 2.If it still fails, retry later from the broadcast

What It Means

The send failed and WhatsApp gave no more specific reason. The error text next to the message has the details.

Common Causes

• An unexpected answer from WhatsApp

How to Fix

1. 1.Read the error text shown with the message
2. 2.Check Integrations > Channels > WhatsApp, then retry
3. 3.If it keeps happening, contact support with the error text