Tangilla Data Imports
Tangilla Data Imports is under Tangilla Data in the left-hand menu. It's where you can trigger a data sync by hand, and see the history of every sync run — scheduled and manual.
Most syncs run automatically on their own schedule; you shouldn't normally need this screen. Use it when something looks out of date and you don't want to wait for the next scheduled run, or when you're troubleshooting a sync that failed.
Running a sync manually
Click the button for the sync you want:
| Button | What it does |
|---|---|
| Sync Events | Pulls in the latest events from your events feed |
| Sync Members | Pulls in the latest member records |
| Sync Affiliates | Pulls in the latest affiliate records |
| Sync EdConnect Courses | Pulls in the latest education courses |
| M1 Members + Offices (NAR) | Runs the full NAR M1 extract — the primary source for member and office records |
⚠️ The M1 sync is a large job. It can take a while and may need re-triggering if it pauses partway through — that's expected on a run this size, not a failure.
⚠️ Ignore the Sync Agents and Sync Offices buttons on this screen. This site has no MLS listings and no agent roster, so those two don't apply here — they're carried over from the shared version of this screen used at other TaliCMS sites. Clicking them does nothing useful at this association.
Reading the log
Every run — scheduled or manual — appears in the table below, newest first: which source, whether it succeeded, how many records were processed/created/updated/skipped, and how long it took. Click View on any row to see its detail, including any per-record errors.
A sync that shows Skipped for most records is working correctly. Most syncs only write records that actually changed since the last run — a high skipped count on a routine run means nothing changed, not that something failed.
If a sync fails
Check the expanded row for the specific error. A single-record error usually means one bad row in the source feed — most syncs continue past it and report it rather than stopping the whole run. A run marked Failed outright, or one that fails again after you retry it, is worth reporting to support along with which source it was.
Related
- What's synced and what you can edit
- Member records, photos and courses