Detect a non-functional messenger integration
The system continuously verifies that a connected Page can still send, receive and be notified of new messages, and tells the Admin precisely why it stopped working when it does.
When this happens: The periodic health check runs (FR-15), or a send/receive operation fails.
Step by step
- 1
Open the connection and sees the specific cause, not just not working.
EasyCRM runs the scheduled health check against the connection: token validity,
pages_messaginggrant, Page publish state and webhook field subscription. EasyCRM detects the token is no longer valid — the Owner who granted it lost their admin role on the Page. SetsTokenRevoked,RequiresReauth. EasyCRM notifies Admins (FR-10 extension): Facebook Messenger (Acme Home & Garden) lost access — reconnect to restore delivery.
Other paths
Page unpublished
The Page is detected as unpublished. Sets PageUnpublished, Error — reconnecting will not fix it until the Page is republished.
Webhook subscription lost
The Page's messages field is no longer present in the app's webhook subscription. Sets WebhookSubscriptionLost, RequiresReauth.
Good to know
- Each failure cause is reported specifically, not as a generic "connection error."
PageUnpublishedis not resolved by reconnecting; the Page itself must be republished first.