WhatsApp replies suddenly stop: disconnect, reconnect, and resync
A merchant enabled WhatsApp order confirmation, then replies stopped arriving: customers confirm but orders never update, or the connect button fails after a number change.
Why this happens
Usually because the webhook subscription expired, the callback URL changed after a domain move, a new number was linked without disconnecting the old one, or Meta app permissions were revoked.
What Vareons does about it
The app provides a Resync webhooks button that re-subscribes and repairs the route through POST /api/whatsapp/subscribe-webhooks, a webhook health panel inside View details for diagnosis, a red Disconnect button with browser confirmation before linking a new number, and a redeploy-templates action for stale templates.
- apps.whatsapp.supported — WhatsApp Automation app: Available
- apps.marketplace.supported — Apps marketplace (install/open/uninstall): Available
Limitations
Resync cannot repair Meta-side revoked permissions; a fresh OAuth may be required. Messages missed during the outage are not received retroactively.
Related problems
Frequently Asked Questions
Replies stopped suddenly, should I delete the app?
No, the issue is operational in the webhook path or the Meta session, and the fix lives inside the app with no reinstall. Start with the resync control and review the health panel before considering any drastic step.
I changed the phone number and linking fails, what now?
Disconnect the old number first through the disconnect control with browser confirmation, then link the new one, since linking over the old session confuses it. After linking, resync the webhook to confirm the receiving path is sound.
Do missed messages arrive after the fix?
No, messages missed during the outage never arrive retroactively, and resync only repairs the future path. Act as soon as the stall is noticed and keep the outage window as short as possible.
Last verified: 2026-09-19