Vinh Cao
May 7, 2024
visibility 2579
star star star star star
(2 votes)

Search & Navigation: Indexing job new features

From Episerver.Find version 16.1.0, we introduced some new features that make the indexing job in CMS more flexible and efficient:

  • Support continuous indexing job. In case the job has been crashed, you can restart and it will continue indexing progress from the last content that has successfully indexed.
  • Allows configuration of the maximum concurrent background tasks used during the indexing job.
  • Allows configuration of how many queue items are loaded per loop when using the continuous indexing job. With this configuration and the maximum concurrent background tasks, you can adjust the job to balance CPU/memory allocations and indexing speed rate as well.

How to enable the new continuous indexing job and other new features

We have some new options that need to be added to appsettings.json file to enable the new continuous indexing job and other new features:

{
    ...
    "EPiServer": {
        "Find": {
            "DefaultIndex": "your_index",
            "ServiceUrl": "https://demo.find.episerver.net/your_key",
            "Cms": {
                "EnableContinuousContentIndexingJob": true, // to enable the new continuous indexing job
                "IndexingJobMaxThread": 4, // to configure the maximum concurrent background tasks 
                "IndexingJobQueueItemLoadMultiplier": 4 // to configure how many queue items are loaded per loop 
            }
        }
    },
    ...
}

You can also learn how to use these new features on our document. Please check it out.

May 07, 2024

Comments

error Please login to comment.
Latest blogs
Finding Thomas Part 3 - The Moment of Recognition

Remember Thomas? In digital landscape, Thomas is the returning visitor who reads everything, opens every email, converts on nothing. In standard...

Ritu Madan | Jun 26, 2026

Add more scheduled job settings from the Optimizely CMS 12 admin UI -- with OptiScheduledJob.ExtraParameters

  Optimizely (EPiServer) CMS 12 ships a great scheduled-jobs framework, but it has one frustrating gap: a job has nowhere to store its own...

Binh Nguyen Thi | Jun 25, 2026

Automated Search & Navigation to Graph Migration with Claude Code

A Claude Code plugin that scans your S&N codebase, applies Graph SDK transformations, and validates the result. Install once, run one command. CMS ...

Connor Fortin | Jun 24, 2026

Migrating from Find to Graph: Lessons Learned from a Real CMS 13 Project

While migrating a search solution from Optimizely Search & Navigation (Find) to Optimizely Graph in CMS 13, I encountered several issues that were...

Binh Nguyen Thi | Jun 24, 2026

Optimizely: Upgrade Opti-ID and .NET 10 in CMS 12

Many Optimizely customers are planning their roadmap around a future migration to Optimizely CMS 13. As a result, upgrades such as Opti ID adoption...

Madhu | Jun 23, 2026 |

Understanding Optimizely Graph: Caching, Webhooks & Avoiding Stale Content (Optimizely SaaS CMS)

📌 Scope: This post covers Optimizely CMS (SaaS) only — using the official @optimizely/cms-sdk and @optimizely/cms-cli packages with Next.js 15. If...

Kiran Patil | Jun 23, 2026 |