Skip to main content
Realtime sync depends on a webhook the provider delivers to Synclify. When that delivery path breaks, syncing does not stop — it falls back to polling — but latency goes from seconds to minutes. Repairs run automatically. That is the headline. Synclify re-registers a broken webhook on its own, and nothing is toasted at you for a repair you did not ask for. The panel described below appears only in the cases that genuinely need a person.

​
The Realtime tile

Every connection shows one Realtime tile:
Polling fallback is not a failure state. It means realtime broke and your polling schedule caught it. Records still sync — just on the poll interval rather than within seconds. A connection with no polling schedule shows Realtime degraded instead, and that one is worth acting on.

​
Re-checking

A health check performs live reads against the provider. That is why it never runs automatically on page load — opening a page should not spend your provider’s rate limit. Use Re-check webhooks on the connection, or Refresh check on a Data Sources account, when you want a fresh answer.

​
When a person is needed

The Realtime webhook health panel renders only for states automatic repair cannot clear:
“Repair is disabled until provider access is reconnected.” Reconnect the account on Data Sources first — nothing else can proceed.
Synclify cannot tell what state the provider is in. Refresh the provider evidence before anything is changed.
A replacement webhook is registered but unproven. It is confirmed by an actual signed delivery, not by the registration succeeding.
A stale registration must be removed before a new attempt can be made. Cleanup targets exactly the identified registrations and nothing else.
Cleanup is confirmed. A new replacement attempt can be authorized.
“Refresh the health check. Repair does not run for an unknown provider state.” Synclify will not act on a state it could not read.
Retry repair queues work; it does not prove it. “Only a later healthy check confirms the provider finished.” A queued replacement stays pending rather than reporting success it cannot vouch for. Re-check before you conclude it worked.

​
Account-level health

Data Sources shows the same picture per connected account, across all its resources at once. Use it when several connections degrade together — that usually means the account, not the connections. The account check is never automatic, for the same reason: each one performs a live provider inventory read.

​
Why realtime breaks

Re-authorizing can invalidate existing webhook registrations. Synclify re-registers them; give it a check afterwards.
A webhook registered against a resource that no longer exists cannot deliver. See Change synced resources.
Providers expire webhook registrations on their own schedule. This is the ordinary case, and the one automatic repair exists for.
Keep a polling schedule on connections that matter, even with realtime working. Polling is what turns a broken webhook into a slower sync instead of a stopped one — see Sync settings.