WhatsApp Coexistence Limitations: What Breaks and What Is Not Synced
Most lists collapse two different outcomes. Some features are disabled in the Business App, while many others keep working there but are not exposed on Cloud API. Meta's current three-column feature table makes that distinction explicit.
The hard platform ceiling is 20 messages per second. The app-side features genuinely disabled are disappearing messages, view-once, live location, and writable broadcast lists. Catalogs, groups, calls, labels, quick replies, and profiles continue in the app.
Three buckets, not one limitations list
Disabled in the app
Disappearing messages, view-once, live location, and editable broadcast lists.
App-only
Groups, calls, catalog, labels, quick replies, profile, status, and Channels still work but do not sync to Cloud API.
Supported or improved
One-to-one chats and contacts sync, while current Meta docs say edit and revoke are supported.
The table below follows Meta's current published feature table, checked 30 August 2026. Provider help centers may lag behind Meta; when they conflict on a Meta-level capability, this page follows Meta.
Meta's current feature table
| Feature | What changes in the Business App | Available through Cloud API? |
|---|---|---|
| Individual chats | Message edit/revoke is supported | Yes; up to 180 days of history can be synchronized |
| Contacts | No change | Yes; WhatsApp contacts can be synchronized |
| Group chats | No change | No; groups are not synchronized |
| Disappearing messages | Turned off for one-to-one chats | No |
| View-once messages | Disabled for one-to-one chats | No |
| Live location | Disabled for one-to-one chats | No |
| Broadcast lists | No new lists; existing lists become read-only | No |
| Voice and video calls | No change | No |
| Catalog, orders, status | No change | No |
| Marketing tools, greetings, away messages, quick replies, labels | No change | No |
| Business profile | No change | No |
| Channels | No change | No |
Linked-device limitations
Meta supports up to four companion clients, except WhatsApp for Windows and WhatsApp for WearOS. All companion apps are unlinked during onboarding; supported ones can be relinked afterward.
Unsupported companions create asymmetric behavior. A person may see or send a message in WhatsApp, but the event may not reach your webhook, and unsupported devices can show placeholder text. Test the devices your staff actually use before rollout.
Operational constraints beyond the feature table
| Constraint | Current rule | When it matters |
|---|---|---|
| Throughput | Fixed at 20 mps | Use API-only for sustained demand above the ceiling |
| Cloud API Calling | Unavailable | Use app calling or move the number to API-only |
| History request | Once, within 24 hours | Missing the window requires offboarding and re-onboarding |
| History scope | 180 days; no groups; media IDs only within 14 days | Archive the webhook stream in your own system |
| Primary-device inactivity | Approximately 14 days can trigger disconnection | Open the Business App regularly; Dualhook warns at 13 days |
| Companion inactivity | Approximately 30 days | Relink inactive companions when needed |
| Deregister API | Blocked for active coexistence numbers | Disconnect through the Business App instead |
| Onboarding eligibility | Provider partner status, app version 2.24.17+, and Meta eligibility checks | A technically correct flow can still be refused |
The “13-day rule” precisely stated
Meta documents PRIMARY_INACTIVITY after approximately 14 days. Dualhook's 13-day heartbeat is a conservative reminder and confirmation timer designed to warn before that Meta window, not a claim that Meta publishes a literal 13-day requirement.
Provider-specific limitations are not Meta-wide rules
respond.io
Echo messages appear in the inbox but do not trigger automation, open a service window, or start a conversation. Its current docs say contact and message-history import is not supported for the coexistence channel.
360dialog
Its current page says OBA, WABA-to-WABA migration, profile-picture changes after onboarding, and Calling API are unsupported for its coexistence setup. Treat those as provider-documented constraints, not rows from Meta's feature table.
Gupshup
Gupshup requires an app account at least three months old with active messaging, no payment method attached to the Business App, and a supported country. Nigeria and South Africa are currently excluded. Its docs also warn of ongoing Meta-side inconsistencies in history, contacts, and message echoes.
WATI
WATI exposes coexistence through its own inbox and plan model. Its USD pricing starts at $59/month billed annually or $69 monthly. WATI describes Growth as 10,000 API calls per month with no webhooks, Pro as 200,000 API calls with limited webhooks, and Business as 20 million API calls with extensive webhooks.
Common failure modes
- 131060: Meta says an unsupported webhook is expected for some first-time messages and unsupported companion devices, and usually resolves within seconds.
- 130429: throughput limit hit; the coexistence ceiling is 20 mps.
- 2593109: the business declined to share history during onboarding.
- 2655093: a stale partner or coexistence relationship blocks Embedded Signup.
- No message echo: the sender may have used WhatsApp for Windows or WearOS.
- No history: the 24-hour request window expired, the request already ran, or the business declined sharing.
Workarounds and migration triggers
- Rebuild broadcasts as approved API template campaigns.
- Keep groups manual in the app because they do not synchronize.
- Keep calls in the app, or use an API-only number for Cloud API Calling.
- Use catalog, labels, and quick replies in the app unless your own system needs API control.
- Open the app regularly and monitor account_update for partner removal.
- Move to API-only for sustained traffic above 20 mps or another hard API-side requirement.
Frequently asked questions
Does my catalog stop working after enabling coexistence?
No. Meta's feature table says there is no change to Business App tools such as catalog, orders, and status. They continue in the app but are not synchronized to Cloud API.
Do quick replies, labels, and away messages stop working?
No. They remain available in the WhatsApp Business App. The limitation is that these app-side messaging tools are not exposed through Cloud API on the coexistence connection.
Which Business App features are actually disabled?
Meta disables disappearing messages, view-once messages, and live location for one-to-one chats. New broadcast lists cannot be created and existing lists become read-only.
Can messages be edited or revoked under coexistence?
Yes. Meta's current table says Message Edit/Revoke is supported for one-to-one chats. Some older provider tables still show the previous limitation.
Is there a 13-day Meta requirement?
Meta documents disconnection after approximately 14 days of primary-device inactivity. Dualhook uses a 13-day reminder threshold as a conservative safety margin, not as Meta's literal rule.
What is the coexistence throughput cap?
Twenty messages per second, fixed by Meta to remain compatible with the Business App. A provider's high-throughput plan does not raise this limit for a coexistence number.
Why did a reply from a linked device not reach my webhook?
WhatsApp for Windows and WhatsApp for WearOS are unsupported companion clients for coexistence webhooks. Messages involving unsupported companions can remain visible in the app without producing the webhook your backend expects.
Can I use Cloud API Calling on a coexistence number?
No. Voice and video calls continue in the Business App, but Cloud API Calling is unavailable for coexistence numbers. Use an API-only number if API calling is required.