Background checks compare both sides and report what does not line up — and what you decide about it.
Synclify runs background checks that compare both sides of a connection. Anything that does not line up is reported as a difference, in the Differences found panel on the connection’s history tab.
Background checks compare both sides and report what does not line up. Only differences waiting on you are listed. Deciding here changes the record of the difference, not the data at your providers.
That last sentence is the important one. Resolving a difference records a decision. It does not edit anything in Airtable or Webflow.
The panel is visible to owners, admins, and support only. Operators and viewers never see it, so if a teammate cannot find it, check their role.
Not every difference offers a decision, and the panel is explicit about which do.
Link records
Offered when Synclify has a candidate. Accept it and the two records are linked, then a follow-up check is queued to confirm: “The two records are now linked. A check is already running and will confirm it.”
Mark resolved
For a difference you have already fixed at the providers. It moves to history.
Ignore
For a difference you accept. “It stays in history and will come back if the next check still sees it.” Ignoring is not suppression — a real problem returns.
Every decision requires a reason, and “The reason is recorded in your workspace audit log.” Write something a colleague could act on in three months, not “ok”.
Some differences cannot be resolved from this panel — they clear themselves once the underlying cause is fixed. Rather than show a row with a disabled button, the panel collapses them to one line: “N differences reported — nothing to decide.”Expanding it names what clears each one:
Difference
What clears it
Record is not linked yet
”An unmatched source row is only created in Webflow when this connection’s record decisions allow it. Review that decision, then run a sync.” There is a Review record decisions link straight to it.
Open conflicts block this check
”Open the run that raised the conflicts and choose a winner there.”
Field or table structure changed
”Re-open the field mapping so the changed fields are picked up, then approve the draft.”
Show history reveals differences that were resolved or ignored. When nothing is open, the panel retires itself entirely — no section, no history toggle. History is a record of decisions, not a standing report.Only the most recent differences are listed at once: “Only the most recent differences are shown. Resolve these and refresh to see the rest.”
A pairing or structural problem — records that don’t line up.
Both sides edited the same two-way field since the last sync.
What you decide
Whether the records are the same thing.
Which value wins.
Effect on data
None. The decision is a record.
The winning value is written.
If differences keep reappearing on the same records, the usual cause is an unstable identity field. A field people rewrite makes every edit look like a brand-new record — see the identity field.
