What happens to moderation while disconnected
While an account is disconnected, moderation pauses for that account’s pages: no new comment is pulled in, so no Workflow runs, and nothing is hidden, replied to, flagged, or deleted. Comments posted during the outage are not processed in real time — but in the normal case they are not lost either. When you reconnect, the app pulls in the backlog and runs your Workflows on it retroactively. The exception is at the bottom of this page: comments the platform no longer returns by the time you reconnect are missed permanently.
What “disconnected” means here
Section titled “What “disconnected” means here”An account is disconnected when its Meta access is no longer valid. In Accounts, that account shows a Re-auth badge (amber) or an Error badge (red), and its pages show Ingestion: Inactive. Ingestion is the app pulling comments in from the platform; while it is inactive, there is nothing for a Workflow to act on.
Disconnection is per account, not global. Your other connected accounts keep moderating normally.
For how accounts reach this state and how to fix it, see Fixing a disconnected account.
Are comments queued or missed?
Section titled “Are comments queued or missed?”Queued, in the normal case. The app tracks how far it has read each page. While the page is disconnected, that marker does not move — it stays at the last comment successfully pulled in before the outage. New comments keep arriving on the platform, but the app is not reading them yet.
When you reconnect, the next sync reads forward from that marker and pulls in everything posted during the gap. Those comments are then processed by your Workflows exactly as if they had just arrived. Already-seen comments are deduplicated, so reconnecting does not create repeats.
This backfill is why a short disconnection is usually recoverable: the work is deferred, not thrown away.
Why reconnect speed is the real control
Section titled “Why reconnect speed is the real control”Because the risk is the platform’s own retrievable window, the length of the outage is what determines whether you lose anything:
- Reconnect within minutes or hours: the backlog is almost always still fetchable, and Workflows catch up on it.
- Reconnect after a long delay: older comments from early in the gap may no longer be returned by Meta, and those are gone from the app’s point of view.
Reconnect as soon as you see the Re-auth or Error state. The reconnect steps are in Fixing a disconnected account.
What the activity log shows for the gap
Section titled “What the activity log shows for the gap”Two surfaces record the outage, and they show different things:
- The account Activity feed (open the account in Accounts, section Activity) records the lifecycle events: the disconnect, the error, and later the reconnect. This is where you confirm when the gap started and ended.
- The Audit Log (Analytics → Audit Log) records Workflow activity — which Workflow fired on which comment. During the gap it shows no entries for that page’s comments, because no comments were pulled in to act on. After you reconnect, the backfilled comments are processed and appear in the Audit Log then.
So the gap does not silently vanish: the Activity feed marks its boundaries, and the absence of Audit Log entries for that page during the gap reflects that moderation genuinely paused rather than acted invisibly.
After reconnect: confirm moderation resumed
Section titled “After reconnect: confirm moderation resumed”Once you reconnect, verify the catch-up actually ran:
- The account badge reads Active (green).
- The account’s pages show Ingestion: Active, and Last monitored updates to a recent time on the next sync.
- Backfilled comments appear in the Inbox and, once processed, in the Audit Log.
Backfill can take a few minutes to appear after reconnect.