Skip to main content
Every run of a connection is recorded. Open a connection and switch to its history tab.

​
The run list

Ten runs per page, newest first:
ColumnWhat it tells you
TimeWhen the run started.
StatusHow it ended.
DirectionSource → Webflow, or bidirectional.
ActionsRecords created, updated, deleted, skipped, failed.
DurationHow long it took.
While the tab is open the list refreshes every few seconds, so an in-progress run updates in place.

​
Reading a status

StatusMeaningAction
succeededEverything applied.None.
running / queuedIn progress.Wait.
partial / partially_succeededSome records applied, some failed.Open the run. Something is wrong with specific records.
failed / errorThe run did not complete.Open the run; check the source and destination account health.
cancelledSomeone stopped it.Records already written stayed written.
partially_succeeded is the status people ignore and shouldn’t. The sync “worked” — but some rows silently didn’t make it into Webflow. Open the run and find out which.

​
Run detail

Click any run to see what it did record by record: what was created, updated, deleted, or skipped, and which records failed and why.
“Item-level details are not available for this run.”Some runs don’t retain per-record detail. The summary counts are still accurate. If you need to know which records failed, run the sync again and inspect the fresh run.

​
Common failure causes

Webflow rejects items missing a required field value. Fill the source column for those rows, or make the field optional in Webflow.
Field-type checks catch most of this at mapping time, but a value can still be rejected at write time — a number out of range, a malformed URL, an option that isn’t in Webflow’s allowed set.
Two source rows with the same identity value can’t both own the same Webflow item. Deduplicate in Airtable.
Heavy polling or a large first sync can hit Airtable or Webflow API limits, which surfaces as a degraded account. Widen your polling interval.
Check Data Sources. A reauth required account stops syncs.

​
Counting runs against your plan

Your plan caps sync runs per month. Settings → Billing shows the count for the current calendar month, in UTC, with a progress bar. Realtime runs count. If a chatty source table is burning through your allowance, widen what triggers a sync — sync fewer columns, or split the table.

​
If a run won’t load

“Sync run unavailable” means Synclify couldn’t fetch it. Retry. If it persists, accept the support report prompt — it attaches the failing request details automatically.