Know when a WhatsApp automation stops: alerts and monitoring
A WhatsApp automation can stop for reasons inside it, such as a failed step or an AI key the provider refused, or outside it: the number disconnected, Meta not delivering its messages, a restriction. Watch both layers. Get alerts for failed runs, refused keys and disconnections, check the number's connection and quality, and read the run log for replies that were skipped on purpose.
easyCoexistence monitors each connected WhatsApp number around the clock and emails you when Meta disconnects it, with the reason, when Meta stops delivering its template messages and again when that lifts, when a run fails on a real message, and when your AI provider refuses your key.
At most one failure email per automation in this span; the Runs tab keeps every failure.
Meta disconnects a Coexistence number whose WhatsApp Business app is not opened on the phone for about this long.
How often to open the app on the phone; messages sent or received through the API do not count as activity.
From this date Meta stops delivering service messages for businesses with no payment method on file.
Recent monitoring timeline entries get_number_health returns with a live snapshot of the number from Meta.
What can make a WhatsApp automation stop answering?
Problems sit in two layers, and an alert strategy has to cover both. The automation layer is your steps, your key and your settings. The number layer is the connection to Meta, the number's standing and its billing on Meta's side. A healthy automation on a disconnected number answers nobody, and a healthy number with a refused key gives no AI replies.
Which problems send you an email?
Alerts go to the email address of the account, in English, Portuguese or Spanish. The alert phone number asked for at signup is not used to send them. Emails exist so that a person answers the customer the automation could not; problems that leave the number working but quiet show up in the dashboard instead. Here is what arrives and what you check yourself:
| What it says | ||
|---|---|---|
| A run fails on a real message | Yes, one per automation every 6 hours at most | "<automation> could not answer <customer>", with the message, the error and "Open the run" |
| Your AI provider refuses the key | Yes, once per incident | "Action needed: your <provider> key stopped working", listing the paused automations |
| Meta disconnects the number | Yes, once per drop | Meta's reason, the time, and a link to reconnect |
| Meta stops delivering templates | Yes, and again when it lifts | The cause, such as a missing payment method, and the steps in WhatsApp Manager |
| A run is skipped | No | The Runs tab shows the reason, such as your recent reply or the 24-hour window |
| Quality drops or Meta restricts | No | The number's page shows Degraded or Banned / restricted, and the timeline records it |
How does number monitoring work?
Two sources, so a drop is caught even when one stays silent. Meta sends account updates by webhook as they happen, including a disconnection with its reason, such as PRIMARY_INACTIVITY for the 14-day rule. A scheduled health check also reads each connected number at Meta: its status, quality rating, messaging limit, throughput, and whether it can deliver business-initiated messages. A number Meta can no longer read is marked Disconnected and emailed about, and changes go on the number's timeline. Suspended numbers, whose subscription ended, are not monitored.
What is the 14-day rule, and how do you stay clear of it?
Meta disconnects a Coexistence number when the WhatsApp Business app on the primary phone is not opened for about 14 days. Traffic through the API does not count, so a number busy with automations can still be dropped if nobody opens the app. Open it on that phone at least every 10 days and let it sync. If it happens, the email names the reason; open the app, wait for it to sync, then press "Reconnect this number" on the number's page. A webhook destination your system used is put back on its own when you reconnect, when it was saved before.
How do you check health yourself?
In the dashboard, the Automations list shows each automation's last run, "runs in 30 days" and how many failed, and the status filter "Needs attention" lists the ones with a refused key, the ones On while their number's automations are off, and the ones with a failed run in 30 days. Each number's page shows its status (Connected, Degraded, Disconnected, Banned / restricted), its quality rating and a timeline. Your AI can check the same things through the MCP connector, and get_number_health keeps working even while billing has lapsed:
"Is my WhatsApp number healthy?"
-> list_numbers, then get_number_health
(quality, status, Coexistence link, last 15 events)
"Did any automation fail this week? Why?"
-> list_automations, then list_automation_runs with status "failed"
"Show me what happened in that run."
-> get_automation_run (each step's input, output, error and timing)What should you do when an alert arrives?
Answer the customer first where one is waiting, then fix the cause. Each alert has one usual fix:
- A run failed: reply to that customer from the app, open the run from "Open the run", and fix the step named in the error.
- A key stopped working: add credit or create a new key, then "Test and save" it under "AI keys"; paused automations restart by themselves.
- The number disconnected: open the WhatsApp Business app on the phone, wait for it to sync, and reconnect from the number's page.
- Templates are not delivered: in WhatsApp Manager, Account tools, Billing & payments, add a card to the WhatsApp Business account itself.
- Quality is Low: pause whatever started drawing blocks, often a template sent to people who did not expect it.
Common mistakes
- Counting on automation traffic to keep the number connected. Messages sent or received through the API do not count for Meta's 14-day rule; only opening the app on the phone does.
- Reading a quiet inbox as a healthy automation. Skipped runs send no email, so check the Runs tab or the Needs attention filter once a week.
- Adding a card to the ad account or the Business Portfolio when templates stop delivering. Meta needs the payment method on the WhatsApp Business account itself.
- Assuming one failure email means one failure. Later failures of the same automation within 6 hours are only in the run history, so open the Runs tab.
Your AI can check the same health through the MCP connector. 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
Do I get a warning before the 14 days run out?
No. The email arrives when Meta disconnects the number, not before. Make opening the WhatsApp Business app on that phone a routine, at least every 10 days.
Can alerts come by WhatsApp or text message instead of email?
Not today. Alerts are sent by email to the account's address, and the phone number collected at signup is not used for them.
Does a failed test send an email?
No. Runs from Try it in the dashboard and from test_automation are marked as tests and never email you, so testing a broken webhook will not fill your inbox.
What happens to monitoring if my subscription ends?
A number suspended for billing is no longer monitored, and its automations stop. Reconnecting it with an active subscription brings monitoring back.
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