Skip to main content
Most Synclify messages tell you exactly what to do. These are the ones where the reason isn’t obvious.

​
My changes aren’t reaching Webflow

Work down this list:
1

Is the connection active?

draft, paused, and awaiting_approval connections don’t sync. Check the status on the connection page.
2

Is the data source healthy?

On Data Sources, a reauth required account stops syncs entirely. Reconnect it.
3

Is realtime degraded?

The connection’s Realtime stat. If it says Webhooks need attention with no polling configured, changes may not sync at all. Run a manual sync, then add a polling fallback.
4

Is the field owned by Webflow?

On a two-way connection, a field set to Webflow owns ignores source changes by design. Check its direction in the mapping.
5

Did the last run partially succeed?

partially_succeeded means some records failed. Open the run in Sync history.
6

Is auto-publish off?

Items may be sitting in Webflow as staged changes, waiting for someone to publish the site.

​
Setup and creation

A collection can back only one live connection. Delete the existing one first — it moves to the Archive. See Delete and archive.
Mark one mapped pair as the ID field — typically slug, name, or title. See Identity field.
Webflow marks the field required, so it must stay mapped. Either map a source column into it, or make the field optional in Webflow.
A mapping crosses type families (text / number / boolean / date-time). Find the mismatched pair and fix it, or change the column type in Airtable.
Shorter intervals get you rate-limited, which slows every sync. Realtime already delivers changes in seconds — polling is only a fallback.
Not an error. Save the required existing-data decision instead and continue.
Recheck the draft after the mapping update. If validation still reports unpaired records, resolve them directly in Airtable or Webflow.The usual cause: the identity column’s values don’t actually match across the two sides.
Return to the connections list and reopen it. If it persists, the backend is unreachable — accept the support report prompt.

​
Editing and approval

Pausing is not editing. Paused connections reject edits. Create an editable draft instead — see Edit a connection.
A draft is pending. Finish Save & Review → Approve before running a manual sync.
Warnings don’t block activation — including “dry-run preview is only available”. Only errors do. Read the warning anyway: it usually means a mapping is legal but not what you intended.
Expected on larger tables. Synclify retries automatically.

​
Syncing

Almost always the identity field. Someone changed an identity value in the source, so Synclify saw a new record and created a new item.Pick an identity column nobody rewrites — a dedicated ID, or a slug that’s frozen once published.
Check Delete orphaned records on the connection. If it’s on, deleting a source row — or renaming its identity value — permanently deletes the Webflow item.
That run didn’t retain per-record detail. The summary counts are accurate. Re-run the sync to get an inspectable run.
A known issue — a later sync can push the source value back. Set that field’s direction to Webflow owns, which is enforced reliably. See Conflicts.
Contact support.
Widen the polling interval, and check whether an Airtable automation is rewriting rows continuously. Every trigger counts against the monthly allowance.

​
Accounts and access

A security check failed — the response didn’t match the request Synclify sent. Reload and retry. Usually caused by completing the authorization in a different browser or tab.
Delete every connection using that account first — deleting moves them to the Archive, which no longer blocks. The dialog lists up to five blockers.
Remove a member, or upgrade. See Billing.
Your session expired or was revoked. Sign in again.

​
Something broke and there’s no message for it

When Synclify hits a server error or can’t reach the backend, it offers to send a support report. Accept it. The report pre-fills your email with the timestamp, the page, the failing endpoint, the HTTP status, and the error code — everything support needs and nobody remembers to include. Add one sentence about what you were doing. That sentence is usually what makes the report solvable. Support: support@syncwebflow.com