This may be something to do with the recent downtime and relocation of SE servers to Colorado; I think that was around the time I started noticing problems.

Chat search is broken, apparently displaying only results up to ~2015.

I guarantee there should be more results for searches like this and this, but nothing is displaying after around autumn 2015. This is very annoying, because there are a lot of things said in chat that I'd like to find again (for example, right now I want to find the mini-reviews of the Belgariad series which I posted in chat in order to turn them into a published mini-review for a blog).

Not a duplicate of Chat search is broken again - that one's from 5 years ago and presumably a different underlying issue.

  • umm.... it's working fine, you searched in a specific room. If you mean it's broken for a specific room you should really mention this in the bug report. Commented Jul 17, 2017 at 8:42
  • 1
    @ShadowWizard It's not working fine, because it's not displaying newer results from that room (which is where I wrote my mini-reviews). I don't know whether there are other rooms whose results aren't displaying. Commented Jul 17, 2017 at 8:43
  • @Sha - yeah, and that's what's broken. I've had trouble searching for stuff that I know was posted in a specific room and not found it.
    – Mithical
    Commented Jul 17, 2017 at 8:43
  • The room is frozen and deleted. I guess this cause it to not be indexed. Commented Jul 17, 2017 at 8:47
  • OK, confirmed it's a bug with deleted rooms, e.g. here on MSE as well. Commented Jul 17, 2017 at 8:50
  • @ShadowWizard The room is indexed, just not after mid-2015. And searchability of that particular room is important, because it's historically been one of the most active chatrooms on the network and there's loads of useful/important stuff in its archives. Commented Jul 17, 2017 at 9:07
  • @Philippe, are you considering fixing our current chat, or are you planning on building something new and better?
    – Luuklag
    Commented Jan 24, 2022 at 12:21
  • @Luuklag I am more curious what made him put this one, out of thousands of open bugs, in review. It's far from being major, more close to very minor. So, random selection? Maybe using some script? No idea. Commented Jan 24, 2022 at 14:13
  • @Shadow Neither random nor a script :-) Commented Jan 24, 2022 at 14:59
  • @Randal'Thor how can you know? Commented Jan 24, 2022 at 15:01
  • 2
    @ShadowWizardHatesOmicron he's a Wizard. Commented Jan 24, 2022 at 15:17

1 Answer 1


Marking this as since we are not going to be able to get to it in the near term due to the difficulty of fixing issues like this in chat (and it's accompanying Elastic service that is used for search indexing). It will stay in our books as an issue to fix if/when we are able to prioritize chat issues like this again.

  • 2
    Wouldn't status-deferred be more appropriate then? "Indicates that the feature request or bug has merit to consider, but will not be implemented or fixed in the near term." Commented Mar 2, 2022 at 13:21
  • @OlegValteriswithUkraine I think the implication of status-deferred is that is absolutely will get done. Declined means, they'll pick it up if and only iff it's still an issue later on. Commented Mar 2, 2022 at 14:17
  • 2
    @AncientSwordRage no. Deferred should mean it might be done. Planned should mean it will be done almost for sure. Declined should mean it will never be done. That's just my common sense, and sadly not shared by SE, hence the terrible mixup all those tags create. But it doesn't matter, when only 1-2 bugs are fixed every month, best case, and there are thousands of bugs.... you can do the math yourself. Commented Mar 2, 2022 at 14:26
  • 3
    "we are not going to be able to get to it in the near term", the info of the status-deferred tag even says something similar "will not be implemented or fixed in the near term". status-deferred seems to be best here. Anyways, someone needs to address the actual meaning of "bug will not be fixed at present time" in the description of status-declined, its description probably needs a change. Commented Mar 2, 2022 at 14:27
  • @ShadowWizardHatesOmicron I'm basing what I said off of a private conversation with CMs/Devs. I agree the tags are confusing (as evidenced by your comments) but I can't change it myself. Commented Mar 2, 2022 at 14:36
  • @AncientSwordRage that does not matter. So they should put an order into this chaos and edit the tags. They don't, so I can't rely on "private conversation", sorry. Commented Mar 2, 2022 at 14:38
  • 4
    @ShadowWizardHatesOmicron I'm telling you how they use it. I'm not saying the tags shouldn't be edited. I'm trying to help you explain the current situation to the best of my knowledge. Commented Mar 2, 2022 at 14:42
  • 1
    @AncientSwordRage I guess so, it's just a little bit confusing... Well, now that we have a standalone post about it, maybe we can agree on a solution that works for everyone (either editing the wikis, adjusting the usage, or both) Commented Mar 2, 2022 at 18:44
  • I think the status-declined tag here is correct. The extended description for the tag has the following text: [This tag] can also come up if the bug report is determined to be valid (i.e. not status-bydesign), but the team has decided not to fix the bug for technical or performance reasons, i.e. that fixing the bug would lead to further performance issues or introduce other bugs. This answer fits perfectly into that. OTOH, the one for status-deferred states that it's for if it's been evaluated as positive on potential but can't be implemented due to external reasons. Commented Mar 3, 2022 at 4:32
  • @SonictheSaveUkraine-hog - "can't be implemented due to external reasons", I also see the word "near-term" in the description of status-deferred btw. Commented Mar 3, 2022 at 6:05

You must log in to answer this question.

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