Sync logs
Two places record what happened during a data sync — one for listings, one for everything from Tangilla. You don't need either day to day. They're for one question: "did the sync actually run, and what happened?"
Listing Sync Logs
Reachable two ways: Listing Sync Logs, a small indented link under Tangilla Data + MLS in the left-hand menu, and a nicer View Sync History & Diagnostics link that appears inside the Listing Sync screen after you run a sync (see Running the data syncs).
Each entry is one sync run. Open one to see:
| Field | What it tells you |
|---|---|
| Sync Type | Full, Incremental, Image, Agent or Manual |
| Status | Success, Partial Success, or Failed |
| Duration | How long it took |
| Listings Processed / Created / Updated / Removed | What the run actually did |
| Images Downloaded / Uploaded | Photo activity |
| Error Count, Errors | How many problems, and what they were |
| Summary | A plain-language description of the run |
These records can't be edited. They're a history the CMS writes and never changes, so they stay trustworthy. Only an Admin can view or remove them at all.
Event Sync Logs (Tangilla)
A record of every Tangilla import run — events, agents, offices and committees. You won't normally need this screen directly: the Tangilla Imports screen (see Running the data syncs) already shows the same information in a friendlier, filterable table with expandable detail. This raw collection exists mainly as the record behind that screen.
When to look here
A member says their listing or record isn't on the site. Check the newest run. If the last successful run was before the record was added or changed, it simply hasn't been picked up yet.
Things look stale. If the newest run is days old, or recent ones show errors, that's worth reporting.
Before reporting a problem. Being able to say "the last run was Tuesday at 3am and reported 14 errors" turns a vague report into something fixable straight away.
If a run shows errors
A small error count isn't necessarily a problem — one unusual record can fail while everything else succeeds. Worth reporting when the error count is large, the same errors repeat every run, or a run fails completely.
Related
- Running the data syncs
- Property listings