Has anyone else noticed a difference in SOSL on a Spring16 prerelease org? The code has not changed for over a year yet our custom search page has stopped finding results for search strings our end users commonly use.

We have compared our full copy to live (the only difference being the pre-release) and live still works as we expect.

Has anyone noticed this or maybe understand what could be the cause?


This was confirmed as a bug by Salesforce and was patched before the Spring16 release.

1 Answer 1


SOSL is by its nature a fuzzy search mechanism.

The underlying indexes can change overtime, and search results are often ranked on more frequently accessed records. This is detailed in the SOSL documentation.

Either one of these factors could explain a difference in search behavior in an org cloned from your production org.

However, anytime a pre-release org is displaying suspicious behavior it is prudent to raise a case to support. Pre-release is not GA, it is pre-release. One of the reasons we pre-release is so that we can discover problems before the actual product release date.

  • Thanks Peter I have raised a Case now but was just interested if it was just me
    – Girbot
    Commented Jan 13, 2016 at 12:37

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .