For the complete documentation index, see llms.txt. This page is also available as Markdown.

Common Errors & Troubleshooting

1. Coexistence Errors

WhatsApp Channel Shows Not Connected

This issue usually occurs when the WhatsApp channel fails to establish a proper connection due to incomplete verification or account restrictions.

Possible Causes

  • Meta Business Account is under review or disconnected

  • Business verification is incomplete

  • Coexistence policy validation failed

Resolution

You can visit the Business Verification and Check Account Quality sections to understand how to complete these steps.

Coexistence Gets Auto-Disconnected

This happens when Meta automatically disconnects the channel due to policy or quality issues.

Possible Causes

  • Policy violations

  • Poor quality rating

  • Interrupted signup

  • Session timeout

Resolution

You can visit the Check Account Quality section to learn how to verify and resolve issues.

Embedded Signup Shows Successful but Not Fully Connected

Even if signup appears successful, backend onboarding may remain incomplete, causing messaging to fail.

Possible Causes

  • Signup shows successful

  • WhatsApp Business app shows connected

  • Meta shows pending

  • Messaging not working

Resolution

You can visit the Retry Onboarding section for detailed steps.

Login Succeeds but Channel Disconnects Later

This is usually related to browser or session issues rather than account configuration.

Possible Causes

  • Cache or cookies issues

  • Pop-ups blocked

  • Session expired

Resolution

You can visit the Retry Onboarding section for step-by-step guidance.

2. New Number connection Errors

Channel Status Shows Pending

This indicates that Meta onboarding is still in progress or verification is incomplete.

Possible Causes

  • Business verification pending

  • Backend registration incomplete

  • Account under review

Resolution

You can visit the Business Verification section to complete the process.

Channel Connection Fails During Setup

This occurs when onboarding is interrupted or required steps are not completed.

Possible Causes

  • Verification incomplete

  • Signup interrupted

Resolution

You can visit the Business Verification and Retry Onboarding sections for guidance.

OTP Not Received

OTP issues are generally caused by formatting errors or telecom restrictions.

Possible Causes

  • Incorrect number format

  • OTP delay or block

Resolution

You can visit the OTP Troubleshooting section for more details.

Number Verification Fails

This happens when the number is already linked to a WhatsApp account.

Possible Causes

  • Number linked to WhatsApp app

  • Not eligible for API

Resolution

  • Delete the WhatsApp account from mobile

  • Wait 24–48 hours before retrying

You can visit the Remove Number from WhatsApp section to understand the steps.

Number Already in Use

This indicates that the number is actively associated with another WhatsApp account.

Possible Causes

  • Active WhatsApp Personal/Business account

Resolution

  • Delete existing WhatsApp account

  • Retry after 24–48 hours

You can visit the Remove Number from WhatsApp section for detailed steps.

3. Common Errors

Number Already Connected with Another Partner

This occurs when the number is already linked to another BSP.

Possible Causes

  • Existing partner integration

  • Number previously onboarded elsewhere

Resolution

  • Go to https://business.facebook.com/settingsAccounts → WhatsApp Accounts

  • Open the Partners section and remove the existing partner

  • If using coexistence, disconnect from WhatsApp Business app

  • Retry onboarding

You can visit the Remove Existing Partner and Remove Partner from WhatsApp Business App sections to complete this process.

4. Meta Errors

Business Does Not Meet Policy Requirements

This error indicates non-compliance with WhatsApp policies.

Resolution

You can visit the Request Review section to understand how to raise an appeal.

Currency Mismatch in WABA

This happens when the payment method currency differs from the WABA currency.

Resolution

You can visit the Create / Access WABA section for detailed steps.

Security PIN Mismatch (2FA Issue)

This occurs when an incorrect PIN is entered.

Resolution

You can visit the Create / Access WABA section for guidance.

Unsupported Post Request

This is usually a temporary onboarding issue.

Resolution

You can visit the Retry Onboarding section for steps.

WABA Limit Exceeded

Meta limits the number of WABAs per Business Manager.

Resolution

You can visit the Create / Access WABA section for more details.

WABA Temporarily Banned / Permanently Disabled

This occurs due to policy violations or poor quality rating.

Resolution

You can visit the Check Account Quality and Request Review sections to proceed.

Business Restricted

This is usually due to invalid or non-compliant website details.

Resolution

You can visit the Request Review section for guidance

The website you entered seems broken. Check the URL to make sure it's correct.

If you are seeing this error, it means the Facebook Crawler (Bot) is unable to access your webpage. Even if the website loads correctly in your browser, the crawler cannot access it to verify your business and confirm whether it is eligible to use WhatsApp messaging services.

Common reasons for this error:

  • Open Graph (OG) tags are missing from your website

  • robots.txt file is missing or blocking Facebook crawlers

  • Your website is not accessible from a US server location, possibly blocked by your hosting provider

Diagnose the Issue

Go to the Facebook Sharing Debugger tool and enter your website URL: 👉 https://developers.facebook.com/tools/debug/

This will show you the exact error so you can troubleshoot accordingly.

If you see a 403 error and Open Graph data is empty:

Your website is blocking the Facebook crawler. You will need to whitelist the facebookexternalhit bot on your server or via your hosting provider's firewall settings.

Additionally, Open Graph tags are missing from your homepage. Add them to your website's <head> section. Replace the details with your own information. If you are unsure how to do this, please contact your developer or hosting company for assistance.

If the error indicates that your robots.txt file is blocking the Facebook crawler, you must add the following code to your robots.txt file. If you are unsure how to update this, please contact your web developer or hosting company for assistance.

You must ensure that your website is accessible from the US region, as the Facebook crawler bot accesses your webpage from US-based servers. Your hosting provider's firewall or security settings may be restricting access from outside your country.

To resolve this, contact your hosting provider or technical team and request them to:

  • Whitelist US region IP addresses

  • Check and disable any geo-blocking rules that may be restricting international access to your website

How to check whether the issue is resolved

Once your applied the necessary changes, please wait for 5 to 10 minutes then you can visit https://developers.facebook.com/tools/debug/ and input your domain then click on "Scrape Again" button and if you are seeing no error and returns 200 as shown below this means everything is good, you can resume the onboarding step now.

Last updated

Was this helpful?