How the Search Application Schedules Content Processing

The Search application automatically schedules both incremental and full processing jobs for knowledge base (internal) and external collections. Content processing jobs render the collection content visible and available to your users for searching.

Incremental jobs process only content in the collection that has changed, and full jobs process all content in a collection.

The Collection Setup page shows the current scheduling for the following content processing jobs:

KB Incremental content update. This job processes changes to knowledge base content. The application schedules knowledge base incremental processing to run every 15 minutes. This job processes a maximum of 10,000 documents at a time, then reschedules itself to process the remaining documents in batches of 10,000.
KB Full content update. This job processes all the knowledge base collection content. This job processes a maximum of 10,000 documents at a time, and the remaining documents are processed in batches of 10,000 by the KB Incremental content update job. You may want to run this job on-demand, in case there is a change in the schema. For example, when an attribute is deleted.
Web Sitemap Incremental content update. This job processes changes or additional sitemaps that define collections content. The application schedules incremental sitemap processing overnight when sitemaps have been updated or changed.
Web Full content update. This job processes external collections content. The application schedules full processing to run once per week.
Index. This job indexes the updated documents. The application schedules these processing jobs automatically, every 15 minutes. The scheduled time and day appear on this button: Index Processing is scheduled to be run at: {date} at {time}. The indexing and maintenance jobs perform the index cleanup tasks.
Indexing and Maintenance. The indexing and maintenance jobs perform the index cleanup tasks. The scheduled time and day appear on this button: Index Processing and Maintenance is scheduled to be run at: {date} at {time}. You may want to run this job on-demand, when you are trying to fix any unforeseen issue with search results or query processing, where regular Index job is not able to resolve it. It doesn't need to be queued if the index is running fine.

You can schedule content processing jobs as follows:

KB Full content update. You can schedule this job to run immediately by clicking KB Full content update is to be run on-demand.
Web Full content update. You can schedule this job to run immediately by clicking Web Full content is to be run on-demand.