Tools
Inspect sync topology, debug matching, edit local state, and export CSVs.
Tools are optional UI pages.
Use them for debugging and local data workflows.
Most setups only need Configure Pairs and Scheduling.
Available tools
What tools touch
Tools mainly work from local files created by runs.
Runtime state:
/config/state.jsonManual policy (blocks, manual adds):
/config/state.manual.jsonProvider captures:
/config/snapshots/...CrossWatch tracker files (used for local backup workflows)
Provider writes depend on the tool:
Sync topology advisor: no provider writes or pair-setting changes.
Analyzer: no provider writes.
Exporter: no provider writes.
Editor: edits local state and policy.
Import datasets reads live provider APIs to populate
state.json.
Captures: restore and clear actions write to the selected provider dataset.
Pick the right tool
Use Sync topology advisor to inspect enabled sync routes before adding more pairs.
Typical: multiple writers, return routes, redundant paths.
Use Analyzer when items didn’t sync.
Typical: missing IDs, missing peers, bad matches.
Use Events when you need the history of a sync or item operation.
Typical: failed writes, unresolved items, repeated attempts.
Use Exporter when you want CSV files for another service.
It converts local runtime state to import-friendly CSVs.
Use Editor when you need to change local state or apply manual policy.
Typical: block an item, fix a local row, seed data before your first sync.
Use Captures when you want a rollback point.
Typical: before cleanup, before switching providers, before bulk list edits.
Related topics
Last updated
Was this helpful?