On this page
Error 2655115 appears in Meta's connection window with the message "This account type doesn't support partner sharing. Contact support for options." Meta does not publish this code, so this article separates what Meta has told us in the message from what we have seen when it occurs. It stops the connection, but it is a decision about the account, not a fault in your workspace.
Symptom
You press connect in Settings, then Channels, then WhatsApp. Meta's window opens and you sign in, but at the point where your WhatsApp Business Account would be shared with VGraple CRM, Meta shows code 2655115 and the message above. No channel is created, and the channel list still reads "No channel connected". Trying again gives the same code. If you have tried several times, the attempts may differ: some through coexistence, some through standard Embedded Signup, and both end the same way.
What is Meta's documentation for this code?
There is none that we could find. Meta's Embedded Signup flow errors table does not list 2655115, and neither does Meta's error code reference for the Cloud API.
The table does list a different partner-sharing error, for an account that is already shared with another partner, whose resolution is to unshare it from that partner or create a new account. If your message is the "already shared" wording, you have that error, not this one.
What have we seen cause it?
We have looked closely at one case. In it, reading the account through our partner access showed three things:
- The WhatsApp Business Account was owned by the customer's own business and was approved and verified.
- The number was already connected to the WhatsApp Business Platform and was also in use on the WhatsApp Business app.
- The only app attached to that account was the customer's own Meta developer app. VGraple CRM's app was not attached at all.
Put together, that points to a number that was already onboarded to the Cloud API through the business's own app, and that Meta's sharing flow would not then share with a partner app. We think that is the explanation for that case. We do not know whether it covers every case, and Meta has not confirmed it.
Other account types might trigger the same message. We have no evidence about them, so we do not guess.
How do I check whether my number is connected to my own app?
Ask whoever set up your WhatsApp. If a developer or another software vendor connected the number, if you ever created an app in Meta's developer dashboard, or if you use a tool that sends through the Cloud API, your number is probably already on the platform through that route.
A second clue is the WhatsApp Business app itself. Meta's own error for a number that is already connected to the platform elsewhere points to the same place in the app, under Settings, then Account, then Business Platform. If a connection is listed there, the number is on the platform already.
If you are not sure, message us from Support inside VGraple CRM and we will check what Meta shows for the account.
Fix
The route below is the one Meta itself documents for a number that is already connected to the platform, and it is the route that worked in the case we saw. It is not a guaranteed cure for every 2655115.
- Plan for what will stop. Disconnecting removes the link between the number and your own app. Anything built on that app, such as a bot, a webhook or an integration, stops receiving messages from this number as soon as you disconnect. Decide whether you can accept that, or move that work to VGraple CRM first.
- Disconnect in the WhatsApp Business app. On the phone, open WhatsApp Business, then Settings, then Account, then Business Platform, and disconnect the current connection. The number, your chats and the app itself stay as they are.
- Wait a few minutes before connecting again. Meta publishes no exact wait for this case, so do not retry the instant you disconnect.
- Connect through VGraple CRM in coexistence mode. In Settings, then Channels, then WhatsApp, press Connect in coexistence mode, not the standard connect option. In Meta's window pick your business and scan the QR code with your phone when asked. Details are in Connect in coexistence mode.
- Approve sharing your chat history when the WhatsApp Business app asks, and import it from the number's card in Settings, then Channels, then WhatsApp.
- If Meta shows an error again, send us the screenshot.
Watch out
Do not disconnect until you have decided what happens to anything that depends on your own app. Messages that arrive while the number is between connections may not reach any system, so choose a quiet moment.
What if disconnecting is not an option?
If the number cannot leave your own app, because other systems rely on it, then it cannot also be shared with VGraple CRM through this flow. In that case the options are on the Meta side:
- Use a different number for VGraple CRM and keep the existing one on your own app.
- Ask Meta, as the message itself suggests, what the options are for that account type. We can raise this with Meta as a Tech Provider, but we cannot tell you what they will say or how long it will take.
Meanwhile the sandbox number in your workspace lets you build flows, draft templates and use the inbox without any connected number. See Try the sandbox number.
What to send us
Message us from Support inside VGraple CRM with:
- A screenshot of the exact error screen, including any session ID Meta shows.
- The phone number in full international format.
- The name of your Meta business portfolio.
With those, we can read what Meta holds for the account and raise it with Meta. We cannot override what Meta decides about an account type.
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| Code 2655115 on every attempt | Possibly a number already on the platform through your own app | Check Settings, Account, Business Platform in the app; disconnect if acceptable |
| Message says the account is already shared with another partner | A different error | Unshare from the current partner, or use a new account |
| Coexistence shows no QR code | A number-eligibility refusal | See Errors 3441045 and 3441034 |
| Meta says you cannot view an asset | A permissions matter | See No permission to view account |
| Connection works but nothing sends | A separate Meta account block | Read the reason on the channel card |
Prevention
Decide early where a number will live. If it is going to run in VGraple CRM, connect it here first rather than first through a custom app or another software vendor and then trying to move it. A number that is shared through one route is hard to share through another. Tech Provider vs BSP explains how the partner model works, and WhatsApp Business app vs API account explains what each account type can do before you choose.