A sync run is one execution of a connector’s sync logic — pull new items from the provider, normalize them, embed them, and store them.Documentation Index
Fetch the complete documentation index at: https://docs.userepo.com/llms.txt
Use this file to discover all available pages before exploring further.
List sync runs
sync:read. Returns recent runs for the organization, newest first.
queued → running → succeeded | failed.How many source items the provider returned for this run.
How many were actually new (or updated) and stored. The difference is items filtered out (already seen, archived, etc.).
Surfaced from the underlying provider/connector error. Repo passes through provider error messages verbatim where possible.
Trigger a sync run
sync:write.
The source/connector to sync.
If
true, discard the sync cursor and re-ingest every source item. Useful after a schema change or to backfill missing access policies. Slower and uses more provider API quota.alreadyActive: true (HTTP 202). Repo enforces “at most one active run per connector” at the database level via a unique partial index — you can’t accidentally double-queue.