Skip to main content
What this builds. Two resync paths — the standalone Integration.resync() and the KB-scoped kb.resync_integration(...) — plus the negative path that raises KbIntegrationNotFound. You’ll end up with. A dispatched (async) resync on the integrations service and a demonstrated typed error when an id isn’t attached to the KB.

Expected output

Both paths trigger the same resync — kb.resync_integration just validates the id is attached to the KB first, returning a typed error instead of a server-side miss.

See also

Add URLs

Ingest URLs with scheduled rescrapes.

Items and folders

Manage items synced from integrations.

KB reference

Every public method.