Refresh VS Rescan VS Rebuild
Once a source is created, you can refresh, rescan or rebuild the source either manually or automatically with a schedule. This ensures that the source is up to date with the system and that source configuration changes are applied.
The three update types attempt to catch and re-index changes for both:
Content: new, modified, or deleted items
Permissions: users and groups allowed or denied to see the items (see Coveo Cloud Management of Security Identities and Item Permissions)
The refresh update type scans items such as content or permission which have been identified by the source system as having been modified since the last update. Once the scan is complete, the items are re-indexed accordingly.
A refresh can be performed manually or automatically through a schedule. It has the smallest impact on resources since it only scans and re-indexes the items that have changed since the last update.
Sources that do support refresh updates may have limitations such as the refresh not catching all types of changes (deleted items, permission changes, etc.).
The rescan update type scans all items within the source. Once the scan is complete, only the content and permissions that have been modified are re-indexed.
A rescan can be performed manually or automatically through a schedule. It has a medium impact on resources since it crawls an entire source but only re-indexes the items that have changed since the last update.
The rebuild update type scans all items within the source. Once the scan is complete, all of the items are re-indexed.
A rebuild operation can only be launched manually. The process can take several hours or days and has the biggest impact on resources since it re-indexes all source items. Therefore, to avoid making unnecessary rebuilds, you should only launch a rebuild when you have made all the desired source or content changes.
You have changed the name of a space in your Confluence Cloud source. A rebuild of the source is now necessary because performing a rescan will only detect the change for pages that are created or modified after the name change.
You have a Crawling Module source and have more than one Crawling Module linked to this organization. If you change the Crawling Module instance with which your source is paired, a rebuild is required to apply your changes.