Sync and freshness
Continuing connections check selected provider scope for new, changed, moved, renamed, deleted, or newly inaccessible items. They do not repeat all processing after every check.
How Sentium detects change
Sentium uses provider notifications where available, incremental polling, daily reconciliation, and an authorized Sync now action. Full reconciliation checks the whole selected scope against Sentium's recorded inventory, but it does not automatically repeat work for unchanged content.
For every provider item, Sentium compares durable provider identifiers, revision metadata, content fingerprints, and recorded scope. The resulting change set drives processing:
- New: create the first immutable source version and process it.
- Changed: create and process a new immutable version.
- Moved or renamed: update source metadata without pretending the bytes changed.
- Deleted, trashed, or inaccessible: record a tombstone and remove the source from current retrieval.
- Unchanged: preserve the current version without downloading or processing it again.
Unchanged files are not redownloaded, reparsed, re-embedded, or reclassified. Derived work is reused only when its input fingerprint, parser version, chunking version, embedding model, and classification policy remain compatible.
Read freshness states
A connection can be current, syncing, stale, degraded, or require reauthentication. File processing can continue after provider reconciliation finishes, so connection freshness and document readiness are shown separately.
See versions and deletions for the history model or troubleshooting when a status does not clear.