Advanced searches such as closed:yes and user:me are returning no results or the wrong results. I'm pretty sure there are closed questions on MSE, for example:

0 results for closed:yes

And these aren't my posts:

16 results for user:me

Even a search for help returns no results.

Also it just seems kinda slow, even when it works.

  • 1
    It appears to be case sensitive. You can tell by the "search options" not including "closed" for the closed search.
    – Kevin B
    Commented Nov 6, 2023 at 19:32
  • 2
    @KevinB And what case works for you? I tried lowercase, Sentence, and CAPS and none of them work. And it used to work before today.
    – Laurel
    Commented Nov 6, 2023 at 19:35
  • 3
    The "Newest" tab for all searches seems to also be broken. Commented Nov 6, 2023 at 19:36
  • lowercase (as shown in the tips) works fine for me on the relevance tab, which seems to be default for me.
    – Kevin B
    Commented Nov 6, 2023 at 19:37
  • 1
    Or actually, it's not just the "Newest" tab. All searches seem to be sporadically sometimes not working for me. Commented Nov 6, 2023 at 19:37
  • 1
    Not only is the advanced search you describe also not working for me (e.g., on StackOverflow), but also for the questions I've tagged (e.g., on Mathematics). It was working fine, but just stopped now a few minutes ago. Commented Nov 6, 2023 at 19:38
  • 1
    yeah, Search also not working for me in the past few minutes. I was able to get results in the "most relevant" tab, but not in the newest, then vice versa
    – Murch
    Commented Nov 6, 2023 at 19:43
  • 2
    And now it's working again as far as I can tell… Anyone else still having problems?
    – Laurel
    Commented Nov 6, 2023 at 19:44
  • 1
    Have you tried closed:yes randomizedresults:no?
    – Laf
    Commented Nov 6, 2023 at 19:46
  • 1
    @Laurel It's also now started working properly for me again, in both of the cases I referenced previously. Commented Nov 6, 2023 at 19:48
  • 2
    @JohnOmielan Someone reported the same thing on MSO. It's probably a different symptom of the same issue.
    – Laurel
    Commented Nov 6, 2023 at 19:50

1 Answer 1


Thank you for the report, we deployed some changes at 19:13 UTC. We started to see service degradation in our monitoring software and began investigating internally. At 19:38 UTC we opted to roll back the breaking change which restored search functionality.

  • And added some kind of regression test? Commented Nov 6, 2023 at 23:17
  • 5
    Our tests didn't catch this due to difficulty scaling the test environments to the same levels of the prod environment.
    – Josh Zhang StaffMod
    Commented Nov 7, 2023 at 2:46

You must log in to answer this question.

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