Sync and Sources
Connectors keep Keystone aligned with systems you already use. Sources is where you verify what landed.
How sync works
- Default cadence is about once per hour (per connector).
- Sync now on a connector card runs immediately.
- Each run reports counts such as new or changed, permission updates, skipped, and removed.
| Situation | Result |
|---|---|
| New or edited supported file | Ingested; facts extracted |
| Unchanged content | Left alone (cheap) |
| Sharing changed | Access updated when needed |
| File gone from the site/folder | Source and sole-source facts removed |
| Unsupported or empty extractable text | Skipped |
| No mappable permissions | Skipped (fail-closed)—fix sharing, then sync again |
Reading Sources
Open Sources to see title, authority, scope, access summary, fact count, and when it was ingested.
Tips:
- Filter or scan for the connector’s documents after a SharePoint sync.
- Open a source to preview content and fact counts.
- Re-extract (operators) re-runs extraction after product improvements; use in batches when you have many documents.
Common issues
Sync is “ok” but I do not see the file
- Confirm the file type is supported (
.docx,.md,.txt, …—not PDF yet). - Confirm the file sits under the site (and folder path) you connected.
- Check the connector card for skipped documents—often permissions that Keystone could not map.
- Confirm you are looking at the right scope filter / that you have access as a member (operators can browse all scopes).
I deleted the file in SharePoint but Ask still answers from it
Run Sync now. Removal is applied on the next successful sync, not instantly when SharePoint deletes the file.
Facts look wrong after I fixed the document
Sync the connector (or wait for the hourly run), then open the source and use Re-extract if the new version is present but facts lagged.
Department content visible too widely
- Connector scope should be a team, not Organization—see Roles and scopes.
- Avoid organization-wide sharing links on that library—see Connect SharePoint.
- Agents should use bound keys—see Connect AI tools.
Best practices
- Sync after important uploads or deletions instead of waiting
- Prefer one connector per department site
- Watch skipped counts after the first sync of a new library
- Use Ask with a unique phrase from a test doc to prove end-to-end ingest