"Search" is not working properly

A question about : "Search" is not working properly

I type something in the Search box, and press return or click Go and it tells me:

Wait 16 seconds - it shouldn't be possible.

(PS. I'm not getting rogue double clicks and I haven't used search within the last few minutes)

Best answers:

• I think you have to post more information.
  'Search' works fine here for both thread and forum (FF).
• I was just about the post the same One-Eye.
  I have been experiencing the very same results when searching the comps board tonight.
• It's been happening to me too.
  Every time I search for something, it tells me I have to wait 15 seconds. Glad I'm not the only one with the problem, thought I was doing something wrong.
• I am still experiencing the same issue ie:
  This forum requires that you wait 15 seconds between searches. Please try again in 15 seconds.
  This is on a PC via FireFox.
• Is this happening all the time for those it is happening to? Or just intermittent?
• One more test:
  Two searches failed.
  The third gave correct results.
• In some periods over the last few days, it has been happening about a quarter of the time when I search using the quick search box - which is enough to make it really annoying. It then operates normally for a period before failing again. It makes no difference whether I press return or click on "Go". It makes no difference whether I type the string or select one from the drop-down autocomplete list. It happens on both forum and thread search. It has never happened on the subsequent second search (which is by default an "Advanced Search"). It has never happened when I go straight to Advanced search.
  Also, despite being told to "wait 15 seconds", a couple of times it has let me "search now" immediately without actually waiting. When you have actually searched in the last 15 seconds everything works properly.
  The only way you should get "wait 15 seconds" is with a double click or a double press of enter. It is impossible to get it any other way. I am positive I am not getting a rogue double click/double enter.
  The point in the OP is the fact that it said 16 seconds indicated to me that there is a definite problem with the function.
• Many others are encountering this problem (eg. HERE). Now the holidays are over perhaps it might receive some attention.
• Adding a 'me too'. Happening pretty much every time I search.
• Ditto - another 'me too'
  Similar comments to weeowens & one-eye. The problem is intermittent, but annoying. It seems to occur more frequently on the first search in a browsing session.
• Still having this issue - two further updates:
  1. A definite tendency for the first search in a browsing session to bring up this fault
  2. I also got the 'Please try again in 16 seconds.' error message.
• I'm having this problem too it's really frustrating. Has anyone figured out how to get it to stop happening?
  Many thanks in advance.
• This is driving me mad.
  Is it only happening on the Comps Board?
  It happens so irrationally it's like it's looking at everyone searching, i.e. if anyone has searched in the previous 15 seconds it objects to someone else searching??
• FALSE "No Results Found"
  A long standing problem with search is that very occasionally (maybe less than 1 in 50) search returns "no items found" (see above) when you know for a fact some results exist. When this happened you could always click "back" and search again immediately without having to wait 15 seconds. Search always worked this second time and it wasted about 2 seconds (although newbies might not know of this foible).
  Now when you get a false "no results found" you have to wait 15 seconds before trying again. As such this is a major annoyance.
  Note - a true "no items found" behaves differently in that it brings up the advanced search page with the following message:
• It's disappointing that this thread is nearly a month old and seems to have attracted no response or acknowledgement from anyone at MSE.
• I am still experiencing much the same as I posted on page one.
  Any solution on the horizon ?
• Hi
  Thanks for flagging it up
  We're aware of it and talking to the techies