London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!

Manh Nguyen
Aug 30, 2024
  589
(1 votes)

Configure your own Search & Navigation timeouts

The main blog Configure your own Search & Navigation timeouts was posted for years but you need copy the code to your application.

We now bring those code to FIND 16.3.0 and you just need to call SetTimeout(/*timeout in milliseconds*/) method fo make your request works. Both Search and MultiSearch request will work with SetTimeout from FIND 16.3.0.

var searchResults = SearchClient.Instance.Search<IContent>().For("alloy").SetTimeout(10000).GetContentResult();

var multiSearchResults = SearchClient.Instance..MultiSearch<IContent>()
                        .Search<IContent>(x => x.For("test1").InField(f => f.Name))
                        .Search<IContent>(x => x.For("test2").InField(f => f.Name))
                        .SetTimeout(10000) 
                        .GetContentResult());

Please contact us if you have any question or feedback.

Aug 30, 2024

Comments

Antti Alasvuo
Antti Alasvuo Sep 3, 2024 06:33 AM

Just to clarify, the point here is that you can set custom timeout per query using the ".SetTimeout(12345)", but still the appsettings.json Find options are also used, so there is one plave were you can set the default timeout, right?

Like so:

"EPiServer": {
  "Find": {
    "TrackingSanitizerEnabled": true,
    "TrackingTimeout": 5000,
    "DefaultRequestTimeout": 10000
  }
}

Can't find link to the Search and Navigation full configuration, but anyone can look at the source of FindOptions class to see all properties that can be set here.

Manh Nguyen
Manh Nguyen Sep 4, 2024 01:54 AM

Yes you're right, DefaultRequestTimeout is a default timeout value for all requests (default is 100 seconds if not config). But from version FIND 16.3.0 you can override that value for the search request by using SetTimeout() to avoid waiting too long if network or server is in a unstable state.

Please login to comment.
Latest blogs
Integrating Address Validation in Optimizely Using Smarty

Address validation is a crucial component of any ecommerce platform. It ensures accurate customer data, reduces shipping errors, and improves the...

PuneetGarg | May 21, 2025

The London Dev Meetup is TOMORROW!!

The rescheduled London Dev Meetup is happening tomorrow, Wednesday, 21st May, at 6pm! This meetup will be Candyspace 's first, and the first one he...

Gavin_M | May 20, 2025

From Agentic Theory to Practicality: Using Optimizely Opal’s Instructions Feature

A practical look at Optimizely Opal’s Instructions feature — from built-in agents to creating and managing custom instruction workflows. Ideal for...

Andy Blyth | May 19, 2025 |

Common Mistakes in Headless Projects with Optimizely

Adopting a headless architecture with Optimizely is a major shift from the traditional MVC-based development that has been the standard for years....

Szymon Uryga | May 19, 2025