I just opened the review tab and saw this:

The answer in question was already deleted at that point. Usually, I'd just put it down to caching, but here, the system obviously knows it's showing me a deleted answer I shouldn't be able to see — as evidenced by the question title's reddish background (CSS: deleted-answer).

This was the "first answers" tab, by the way.

2 Answers 2


I fixed this, however it does leave an edge case. Some times due to caching a we will have deleted posts in the cache, in these cases we simply omit displaying them during render.

The side effect is that sometimes it will tell you you are looking at 30 posts when, in fact, you are looking at 29. I hope nobody notices that.

  • "I hope nobody notices that." Subtle. Commented Nov 22, 2011 at 3:41
  • All right. Now that that's out of the way, you could look into why I was never notified of this answer and just stumbled upon it randomly. :P
    – a cat
    Commented Feb 19, 2012 at 1:25

It actually is an issue of caching. While it's relatively inexpensive to check before rendering whether or not a particular post is currently closed and/or deleted, generating the underlying list of post IDs for review is a much more expensive process. So, if a post was closed or deleted since the list of reviewable post IDs was generated it's possible for it to still appear until the list is regenerated.

Now, as for why the system doesn't replace that post with another (or less ideally just drop what you can't see from the results), I'm not sure, although once upon a time waffles was looking into it.

You must log in to answer this question.

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