u/Candid_Elderberry162 — reddlx

Hey everyone,

We’re a WhatsApp BSP / integration provider and currently facing a strange issue with WABA Coexistence.

Problem:
Some clients connect successfully via Embedded Signup, everything works fine initially, but after ~1–3 hours we receive:
event: PARTNER_REMOVED

The issue is:
➡️ there is no disconnection_info at all
➡️ looks like it’s initiated by the system (Meta), not the user

What makes it confusing:

Same onboarding flow
Same integration
Some clients work perfectly (no disconnects)
Others get disconnected within hours

Important notes:

No mass messaging / no high load
Happens even when account is basically idle
Clients claim they didn’t log out or change anything
Happens shortly after successful connection

Things we suspect:

Device conflicts (WhatsApp Web / multiple devices?)
Incomplete onboarding / QR flow not fully finalized
Meta internal checks after connection
Possible bugs in Coexistence routing

Questions:

Has anyone experienced random PARTNER_REMOVED without disconnection_info?
Could this be related to linked devices or WhatsApp Web usage?
Is there any way to stabilize Coexistence connections after onboarding?
Are there hidden requirements after Embedded Signup (like activity, message exchange, etc.)?

Any insights would be super helpful 🙏
This issue is hard to debug since Meta doesn’t provide a reason.

Thanks!