Skip to main content

​
Overview

Knowledge base syncing automatically detects changes in your external sources and keeps your documents up to date. When files are added, modified, or deleted in the source, Noxus detects the change and updates the knowledge base accordingly.

​
Supported Sources

SourceDetection MethodSync Intervals
OneDriveFull folder listing comparisonEvery 5 min – 12 hours
Google DriveFull folder listing comparisonEvery 5 min – 12 hours
SharePointFull folder listing comparisonEvery 5 min – 12 hours
WebsiteURL reachability + re-scrapeDaily, Weekly, Bi-weekly, Monthly

​
Enabling Sync

There are two ways to enable sync:

​
After uploading from an external source

When you upload files from OneDrive, Google Drive, or SharePoint, Noxus will offer to enable sync automatically. You can configure the polling interval and whether to delete documents when they’re removed from the source.

​
From the Syncs tab

  1. Navigate to your knowledge base
  2. Click the Syncs tab
  3. Click Enable Sync (appears when your KB has documents from a syncable source)
  4. Configure the sync interval and deletion behavior
  5. Click Enable Sync
You can also enable sync from the context menu on any synced document — right-click and select Enable Sync.

​
Managing Syncs

The Syncs tab shows all active sync triggers for your knowledge base:
  • Resource: The folder or files being watched
  • Provider: The source type (OneDrive, Google Drive, etc.)
  • Sync Config: The polling interval
  • Status: Current sync state (Synced, Waiting, Failed, Paused)
  • Actions: Force sync, edit settings, or stop syncing

​
Force Sync

Click the play button (▶) to trigger an immediate sync. This bypasses the polling interval and runs the sync workflow right away. The result appears in the Ingestion Runs tab.

​
Edit Settings

Click the pencil button (✏) to change the polling interval or deletion behavior for an existing sync.

​
Stop Syncing

Click the trash button (🗑) or right-click a synced document and select Stop Syncing. This removes the sync trigger. Documents already in the knowledge base are not affected.

​
How Changes Are Detected

​
File-based sources (OneDrive, Google Drive, SharePoint)

On each sync cycle, Noxus lists all files in the watched folder and compares against the known state:
  • New files: Files in the folder that aren’t in the KB → downloaded and ingested
  • Modified files: Files with a different lastModifiedDateTime → file content updated in-place, document re-ingested (same document ID preserved)
  • Deleted files: Files in the KB that are no longer in the folder → document removed from KB (if deletion is enabled)
The first sync establishes a baseline — it records what files exist without making changes. Subsequent syncs detect differences from this baseline.

​
Websites

Website sync re-scrapes all known URLs on each cycle:
  • Each page is re-scraped at depth 0 (single page, no link crawling)
  • If a URL returns an error (404, connection refused), the document is marked as deleted
  • The original page title is preserved as the document name
Website sync intervals are longer (daily to monthly) since web content changes less frequently than cloud files.

​
Sync Status

StatusMeaning
Synced (green)Last sync completed successfully. Shows time since last sync.
Waiting for first syncSync was just enabled, hasn’t run yet.
Failed (red)Last sync encountered an error. Hover for details.
Paused (errors) (red)Too many consecutive failures — sync paused. Use Force Sync to retry.

​
Cloud Icon

Documents from synced sources show a small blue cloud icon (☁) next to their name in both the file tree and the document table. This indicates the document is being kept in sync with an external source.

​
Ingestion Runs

Sync operations appear in the Ingestion Runs tab alongside regular document ingestion. Each force sync or scheduled sync creates a workflow run that you can inspect for progress, errors, and warnings.