I was going through some close votes through the review queue, when it showed me this:


Which I had already voted to close on Feb 19, and so am no longer allowed to vote to close this again.

Why did it show up? Anyways, it looks like a bug.

I do see some duplicates, but they are all apparently bug reports which were fixed a long time ago, and this happened today, so not sure if I vote to reopen those old duplicates, or post as new bug, guessing the second.


This is supposed to be prevented - there's logic to make sure you haven't voted to close a given question before showing it to you in the close queue.

...However, it doesn't verify that you haven't flagged it for closure. Which in this case, you did.

It's pretty rare that someone gets the chance to both flag and vote for closure, but the logic could probably be expanded to check for both.

| improve this answer | |
  • I just recently went over 3k (since feb 19), is that the only way this can happen? – Corley Brigman Mar 17 '14 at 16:25
  • It's the most likely scenario, yeah. Still rare, but we've had a few reports of this in the past. – Shog9 Mar 17 '14 at 16:26
  • @Shog9 I got one of these about a month ago as an audit - I failed and wanted to see which stupid user closed it - and I was one of them - not just a flag – mmmmmm Mar 17 '14 at 18:23
  • That... sounds like something else, @Mark. – Shog9 Mar 17 '14 at 19:04
  • So is this status-we-will-fix-it-if-someone-wants-to? – hichris123 Mar 18 '14 at 0:53
  • Pretty much. It's a really, really easy fix if someone happens to be in the code already; probably not worth opening otherwise. – Shog9 Mar 18 '14 at 0:58
  • 3
    The next build will include the fix @Shog9 so eloquently pointed out. It will verify that you haven't flagged it for closure before giving you a task. – Geoff Dalgas Mar 18 '14 at 16:51

You must log in to answer this question.

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