Tools
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
Analyzer: find why an item didn’t sync.
Exporter: export runtime state to import-friendly CSV.
Editor: edit local tracker data, state, and policy.
Snapshots: snapshot and restore provider datasets.
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 snapshots:
/config/snapshots/...CrossWatch tracker files (used for local backup workflows)
Provider writes depend on the tool:
Analyzer: no provider writes.
Exporter: no provider writes.
Editor: edits local state and policy.
Import datasets reads live provider APIs to populate
state.json.
Snapshots: restore and clear actions write to the selected provider dataset.
Back up /config/state.json and /config/state.manual.json before risky edits.
Create a snapshot before destructive provider actions.
Pick the right tool
Use Analyzer when items didn’t sync.
Typical: missing IDs, missing peers, bad matches.
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 Snapshots when you want a rollback point.
Typical: before cleanup, before switching providers, before bulk list edits.
Related topics
Last updated