‎SharePoint suggestions api has stopped returning results‎

[ishanisuchak]

Target SharePoint environment

SharePoint Online

What SharePoint development model, framework, SDK or API is this about?

SharePoint REST API

Developer environment

Windows

What browser(s) / client(s) have you tested

• 💥 Internet Explorer
• 💥 Microsoft Edge
• 💥 Google Chrome
• 💥 FireFox
• 💥 Safari
• mobile (iOS/iPadOS)
• mobile (Android)
• not applicable
• other (enter in the "Additional environment details" area below)

Additional environment details

• browser version: 92.0.4515.159
• SPFx version
• Node.js version
• etc

Describe the bug / error

I have a custom search solution that uses search suggestions api:

/_api/search/suggest?querytext='tes'&inumberofquerysuggestions=10&fprequerysuggestions=true&fprefixmatchallterms=true&culture=1033

This api endpoint used to work before but has started returning empty results lately.

I also checked on other tenants as well, the api doesn't return results on all tenants (it used to return results before).

I have a query suggestions text file in place as explained here

Steps to reproduce

1. Login to any SharePoint online tenant
2. Add a query suggestions text document like the one attached by following steps mentioned here
3. Try to query the suggestions after waiting for at least 24 hours
4. Test the api endpoint after 24 hours of waiting: /_api/search/suggest?querytext='tes'&inumberofquerysuggestions=10&fprequerysuggestions=true&fprefixmatchallterms=true&culture=1033
   QuerySuggestions_alwayssuggest.TXT

Expected behavior

If the query suggestions have been added, the suggestions api should return suggestions for any text that belongs in the suggestions text file

[bcameron1231]

I am seeing this as well in my environments.

[RiddhiKarani]

@VesaJuvonen any update on this we have customers asking for suggestions not returning data?

[github-actions]

Thank you for taking the time to file an issue. We periodically archive older or inactive issues as part of our issue management process, which automatically closes them once they are archived.

If you’d like to understand more about why and how we handle archived (closed) issues, please see Our approach to closed issues.

We appreciate your contribution and if this is still an active issue with the latest SPFx versions, please do resubmit the details. We needed to perform a cleanup, so that we can start with a clean table with a new process. We apologize for the inconvenience this might cause.