Reconnect a number Meta disconnected after 14 days (PRIMARY_INACTIVITY)
When the WhatsApp Business app on the primary phone goes about 14 days without being opened, Meta ends the Cloud API side of a Coexistence number and reports the reason PRIMARY_INACTIVITY. To bring it back, open the app on that phone and let it sync, then run the Embedded Signup flow again with the same number. The app, its chats and the number itself are untouched.
easyCoexistence emails the owner the moment Meta reports the drop, and the number's page says why: "Meta disconnected it because the WhatsApp Business app on the phone was not opened for about 14 days", next to a "Reconnect this number" button.
Primary device inactivity behind the PRIMARY_INACTIVITY disconnection reason.
The initiated_by value in Meta's example PARTNER_REMOVED payload for PRIMARY_INACTIVITY: the platform ended it, not a person.
The account_update event Meta sends when a business re-onboards to the same partner after offboarding.
Window after an onboarding to synchronize contacts and chat history, usable once per onboarding.
How often our dashboard advises opening the app on the primary phone, a margin under Meta's rule.
What does PRIMARY_INACTIVITY mean?
It is the reason Meta gives when it removes the API from a Coexistence number because the primary device went quiet. Meta sends an account_update webhook with the event PARTNER_REMOVED, and inside disconnection_info the reason reads PRIMARY_INACTIVITY, documented as the primary device being inactive for approximately 14 days. In Meta's example payload, initiated_by is SYSTEM.
The primary device is the phone that holds the number in the WhatsApp Business app. Nothing changes on it: customers keep writing, the team keeps answering, and the chats stay where they were. What stops is everything on the API side. Sends through the Cloud API fail, webhooks stop arriving, and automations, AI replies and connected systems go silent on that number until it is reconnected.
Why does nobody notice the drop?
Because the people closest to the number are on the phone, and the phone keeps working. The app does not show a banner when the API side ends, so a shop can run for days believing its automations are answering while customers get replies only when someone happens to pick up the phone.
The usual pattern: the business connected the number, set up an AI reply or a webhook to its system, and then let the team work from WhatsApp Web or a second device while the main phone sat in a drawer. Linked devices do not keep the primary phone active. WhatsApp also says that a primary device left inactive for a long period logs the account out of its companion devices, so the drawer phone eventually takes those with it too.
What has to be redone after reconnecting?
A reconnection is a new onboarding through Embedded Signup, so a few things come back as fresh decisions rather than carrying over.
- The webhook destination. Meta stores it as an override on the provider's app subscription, and
PARTNER_REMOVEDuninstalls it along with the app. It must be applied again. - Chat history. The app asks again whether to share it, and a new 24-hour window to synchronize contacts and history opens.
- Tokens issued to the old connection may not work. Fetch credentials again after reconnecting.
- Meta keeps the existing Messaging account ID for Coexistence, so the WhatsApp Business Account is the same one as before.
What happened to messages sent during the gap?
They reached the WhatsApp Business app on the phone like any other message, so nothing was lost for the business. Your systems, though, received nothing for that period, because the provider's app was uninstalled from the account. An automation could not answer those chats and an AI agent never saw them.
After reconnecting, read the chats that arrived during the gap in the app and answer the ones still waiting. If your own system needs those messages, the history sync offered with the new onboarding is the one way to pull them in: up to six months of one-to-one chats, when the business accepts sharing and a direct webhook destination is saved within 24 hours of reconnecting. A number with automations on does not get the import.
How do you stop it from happening again?
Open the WhatsApp Business app on the primary phone regularly, with the phone online, and let it sync. Meta frames the rule around the primary device, and in our monitoring, messages sent or received through the API do not count as activity on it. Meta publishes an approximate figure, about 14 days, not an exact hour, so a weekly habit leaves a comfortable margin.
Practical ways businesses handle it: a recurring calendar reminder for whoever owns the phone, keeping the primary phone at the front desk rather than in a drawer, and answering at least some chats from the phone instead of only from WhatsApp Web. Monitoring that reports the drop the same day turns a silent week into a few minutes of downtime.
How is it different from other disconnections?
The reason field separates a quiet phone from a number that is really gone, and each one has its own fix.
PRIMARY_INACTIVITY: the app went about 14 days unopened. Open it, then reconnect the same number.COMPANION_INACTIVITY: a linked device went about 30 days unused. Open the app on the phone, then reconnect.USER_RE_REGISTERED: the number was registered on a new device. Reconnect from the phone that holds it now.CHANGE_NUMBERorBUSINESS_DOWNGRADE: a different number, or back on the consumer app. A new connection is needed.- A restriction is an enforcement decision, not a disconnection. Reconnecting does not lift it.
How to set it up
- Open the app on the primary phoneOpen WhatsApp Business on the phone that holds the number, with mobile data or Wi-Fi on, and wait until the chats finish syncing.
- Start the connect flow againOn the number's page in the dashboard, click "Reconnect this number", or start Embedded Signup from your provider, and log in with a Meta account that administers the business portfolio.
- Choose the same portfolio and numberPick the same business portfolio and WhatsApp Business Account. In our experience Meta recognizes the number and offers, pre-checked, to restore what it had before.
- Confirm on the phoneScan Meta's QR code from inside the WhatsApp Business app, confirm the connection and decide whether to share chat history.
- Check delivery end to endConfirm the webhook destination is set, send a test message from a customer phone, and check that your automation or system answered it.
Common mistakes
- Running the connect flow while the phone is still offline or the app unopened. Open the app and let it sync first, or the reconnection can fail on the phone step.
- Assuming the webhook destination came back with the connection. Meta removes it with the app, so your system stays silent until it is set again.
- Treating PARTNER_REMOVED with PRIMARY_INACTIVITY as a customer who left. It is the most recoverable disconnection there is.
- Relying on WhatsApp Web activity to keep the number alive. The rule watches the primary phone, and an idle primary also logs out its companions.
After reconnecting, the saved message destination is put back automatically and automations answer again. US$ 9 down to US$ 0.75 per number per month, falling as you add numbers, with the first 3 days free.
easyCoexistence is a multichannel API and MCP server that connects AI agents such as Claude and ChatGPT to WhatsApp, Instagram, TikTok, Facebook and more. On WhatsApp it uses Coexistence: the business keeps using its number in the WhatsApp Business app while the AI works through Meta's official API.
Frequently asked questions
Is it exactly 14 days?
Meta documents it as approximately 14 days of primary device inactivity and publishes no exact hour. Opening the app at least every 10 days, or weekly, avoids the edge.
Do my customers notice the disconnection?
Not directly. Their messages reach the app on the phone as usual. What they notice is that automatic replies stop until the number is reconnected.
Can my agency or developer reconnect it for me?
They can run the browser part with a Meta login that administers the portfolio, but the confirmation happens in the WhatsApp Business app, so someone with the phone has to take part.
Am I charged while the number is down?
With easyCoexistence the number stays on your plan while it is down, since catching this drop is what monitoring is for, and reconnecting does not add a charge. Remove the number to stop billing.
Keep reading
Ready to get started?
Set up WhatsApp Coexistence in minutes, not months. The app keeps working on the phone.
Start Free TrialVerified on