Refresh and re-sync knowledge
Re-index changed content, use recurring website refresh where available, and choose a safe re-sync.
1 min read
- Project
- Knowledge
- Select a website source
Open the existing website source from Knowledge to edit its crawl configuration or start another scrape.
Re-process the current source once it is idle; reserve a hard website re-sync for a real information-architecture change.
- Finish with
- Fresh content without unnecessary duplicate runs
Use normal re-sync for current contentFirst confirm the source is idle and still correctly configured.
Review URL and crawl settings, confirm URL authority attestation, select re-sync, then inspect changed pages and test the affected question once Ready. Website re-sync re-scrapes; file re-sync re-processes the upload; text re-sync re-indexes saved text.
Use hard re-sync only for structural website changeIt rebuilds folders and schemas, not a single missing answer.
Normal URL re-sync can reuse the latest taxonomy snapshot. Hard re-sync rebuilds it from scratch after substantial information-architecture changes. It does not change the file/text pipeline.
Check recurring refresh as evidence, not an assumptionA scheduled run may be skipped for several legitimate blockers.
Scheduled refresh is plan-gated and requires at least a 12-hour interval. A run can skip when not idle or due, unattested, archived for capacity review, or rate-limited. Check last synced time and run history; change settings only when the source is idle.
Last updated on