Troubleshooting
Coexistence issues
What to do when a coexistence connection does not finish, does not sync or drops.
Each symptom below follows the same shape: what you see, the cause and what to do. The connection walkthrough is in Connect WhatsApp.
Before connecting
Section titled “Before connecting”- The number is active in the WhatsApp Business app 2.24.17 or newer.
- You are an admin of the Meta business portfolio.
- In the panel, you are an owner or admin with 2FA on.
The number is not on the WhatsApp Business app
Section titled “The number is not on the WhatsApp Business app”- Symptom:
422coex_not_on_business_app. - Cause: in coexistence the number must be on the phone’s WhatsApp Business app, and this one is not.
- What to do: install and activate the number on the WhatsApp Business app, or connect in the New number, API only mode.
The Meta window ended without a number
Section titled “The Meta window ended without a number”- Symptom:
signup_incomplete. The window created or picked the account but did not finish with exactly one number. - What to do: connect again and pick (or add) the number in the Meta window all the way to the end.
The session expired
Section titled “The session expired”- Symptom:
signup_session_expired(410). - Cause: the connection session lasts 30 minutes and ran out, or it was canceled.
- What to do: start again from the panel or the connection link.
Permissions were left unchecked
Section titled “Permissions were left unchecked”- Symptom:
signup_scope_mismatch. - Cause: the Meta window finished without the permissions to manage and message through the account.
- What to do: connect again and keep every permission checked.
The popup does not open
Section titled “The popup does not open”- Cause: the browser blocked the Meta popup.
- What to do: allow popups for the panel address and try again. Do not close the panel page while the popup is open.
Account banned or flagged
Section titled “Account banned or flagged”- Symptom:
403account_flagged. - Cause: Meta banned or flagged the account. Messajo refuses before changing anything at Meta.
- What to do: resolve it with Meta in WhatsApp Manager. Once cleared, connect again.
Number already connected
Section titled “Number already connected”- Symptom:
409connection_already_existsorwaba_owned_by_other_org. - Cause: the number already has a live connection, in your organization or another one. A WhatsApp Business Account (WABA) belongs to a single organization.
- What to do: use the existing connection. To move it to another organization, disconnect it there first.
The number is already with another partner
Section titled “The number is already with another partner”- Cause: in coexistence the number accepts one partner at a time.
- What to do:
- Back up the chats in the app.
- In the app, go to Settings > Account > Business platform > Disconnect.
- Connect again through Messajo.
- The previous partner receives the
PARTNER_REMOVEDnotice from Meta.
The connection stayed Pending
Section titled “The connection stayed Pending”- Cause: a step after the subscription failed. The panel shows the reason.
- What to do: on the connection page, Finish connection redoes what was missing, without the popup. The History tab shows every step, including where a cancellation in the popup happened.
History or contacts did not arrive
Section titled “History or contacts did not arrive”Open the connection’s Sync tab.
| Status | What to do |
|---|---|
| Queued | Wait. It has not been requested yet, or will be requested again after a failure |
| Requested from Meta | Wait. Meta accepted and is sending the data |
| Completed | The data arrived: contacts in contacts.sync, chats in history.batch |
| Declined | The person declined to share history on the phone |
| 24 h deadline passed | Meta only accepts the request up to 24 h after connecting |
The sync is requested once. If the request fails, Messajo retries at 1 min, 5 min, 15 min, 1 h, 3 h and 6 h, always within the 24 h. Groups do not sync.
The connection dropped on its own
Section titled “The connection dropped on its own”- The app must be opened every ~14 days, a Meta rule for every number in coexistence.
- The number left the WhatsApp Business app: the connection emits
connection.updatedwithreasoncoex_unlinked. - The account removed Messajo as a partner: the connection becomes Disconnected with
reasonpartner_removed.
The reasons and what to do for each status are in When the connection drops and Connection reasons.
I cannot edit profile, name or username through the API
Section titled “I cannot edit profile, name or username through the API”- Symptom:
422coex_not_supported. - Cause: in coexistence Meta does not let the API change the profile, display name or username.
- What to do: change it in the WhatsApp Business app on the phone, or use an API-only number.
Limits that look like bugs
Section titled “Limits that look like bugs”- Fixed speed of 20 msg/s. Above it,
429connection_rate_limitedwithRetry-After. See Limits. - Calls:
calling_not_supported_in_coex. Use an API-only number. - Groups:
group_not_supported. Use an API-only number. - A message sent from the phone arrives as
message.echoand does not open the 24 h window: only the contact’s message does. See Windows.