Skip to Main Content
Customer Feedback

We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.

For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.

Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.

Status Investigating
Created by Guest
Created on Mar 3, 2021

Consider including an option to control request timeout for unifiedsearch

Hello,

my client recently ran into an issue where intermittent network-failures caused Find-calls to time-out. In order to mitigate similar issues it would be convinient if there was some way to control the timeout through the public API. Here are a few modest suggestions where any or all would do:

  1. Add an async overload for EPiServer.Find.ClientExtensions.UnifiedSearchFor with a cancellation-token parameter.

  2. Add a timeout-property to EPiServer.Find.IClient.Settings

  3. Add a timeout-parameter to EPiServer.Find.SearchExtensions.GetResult


  • Optimizely
    Martin Ottosen
    Reply
    |
    Jun 28, 2024

    Thanks for the suggestion, we have a few things happening that will help here.

    We are adding a "SetTimeout()" extension to the query builder. example below

    client.Search<T>() .SetTimeout(10) .GetResult()


    We are also putting finishing touches on a set of awaitable async methods.