Meta connection revoked — how to reconnect

If your dashboard shows "Meta connection inactive" or you stop receiving messages and Lead Ads, the most common cause is that the access token Zymblerwas using got revoked on Meta's side.

The fix is a 30-second reconnect — but it's worth understanding what triggered the revoke so it doesn't happen again.

Long-lived tokens normally don't expire. They die only when:

• Someone removed Zymbler from Business Integrations. In Facebook Settings → Business Integrations, anyone with Admin access can revoke connected apps.
• The Facebook user who originally connected was removed. Page Access Tokens are tied to a user. If that user loses Admin rights on the Page (or leaves the company), their tokens die.
• The Facebook account password was changedAND the user enabled "invalidate all sessions" during the change.
• The Page or WABA itself was deleted.Less common but recoverable only by un-deleting the asset within Meta's grace period.
• Meta's automated system flagged the integration. Rare — usually accompanied by an email explaining why.

1. In Zymbler: Settings → Integrations → Meta.
2. You'll see a banner saying the connection is inactive → Reconnect.
3. The Meta OAuth popup opens. Sign in with the same Facebook account that originally connected (or with another Admin if the original user left).
4. Select your Business Account, Pages, and WABA again. Confirm permissions.
5. Popup closes; Zymbler stores new tokens and re-subscribes webhooks automatically.

Your existing flows, lead history, and configurations are untouched — reconnecting only refreshes the credentials.

• Don't remove Zymbler from Business Integrationsunless you mean to disconnect. The Business Integrations page lists every app you've ever connected — it can look cluttered, but removing entries breaks them.
• Keep at least two Admins on the Business Account, on each connected Page, and on the WABA.
• Don't change the original connector's Facebook password from a public/shared device.If you have to, choose "Don't log out other sessions" on the password change form.
• Add Zymbler as a tested-and-trusted app in Business Integrations — this hides the bulk-remove option for critical integrations.

Conversations that started while Zymblerwas connected stay in your inbox. They're read-only until reconnection:

• Inbound messages from the revoked period are not received — they go to your WhatsApp Business inbox in Meta's UI directly, where you can see them at business.facebook.com/wa/manage/messaging. After reconnect, new messages flow again but you'll have a gap.
• Lead Ads data delivered during the revoked period is queued by Meta for up to 7 days. After reconnect, Zymbler fetches any queued leads automatically.
• Outbound messagesfrom the AI agent stop the moment the token dies. The agent doesn't retry until reconnect.

For this reason, reconnect quickly if you notice the banner. Set up uptime monitoring on your Zymbler workspace so the team sees revokes within minutes, not days.