Back in April, I flagged a post as "not a real question". The post was subsequently closed and reopened, then closed again and finally just reopened a 2nd time a short time ago.

I still firmly believe the post is not acceptable for SO, so I went to use my recently acquired close vote privilege and was greeted with the following messsage:

enter image description here

I specifically clicked close and not flag (and figuring I just clicked in error, I tried again and got the same message).

I do understand that, in the new closing system, flagging for closure is treated very much like a close vote (since it throws it to the close vote queue) except no vote is actually recorded. My issue is why should by flag be counted as a close vote when I never actually voted to close.

  • Just curious, what question?
    – RyPeck
    Aug 14, 2013 at 1:32
  • 2
    @RyPeck This is a general question, but this meta post should answer that question: meta.stackexchange.com/questions/193136/… Aug 14, 2013 at 1:39
  • I can see if a person had flagged for closure and then not be able to vote for closure if the question was never closed, but according to the post, the OP had flagged for closure, and the question was subsequently closed and then reopened. Shouldn't the original close flag then no longer count toward future actions at the point of closure?
    – RobH
    Oct 30, 2013 at 16:45

1 Answer 1


After some discussion, a change is being pushed out to allow users that previously flagged for recommend closure to then cast a full close vote, after they've attained the appropriate privilege. The main justification being that this new privilege supersedes the old and you should be able to exercise that privilege.

As Martijn pointed out in this question's comments and Shadow in an answer, this could lead to questions being put into the close review queue twice by the same user. However, this theoretically shouldn't happen often, due to the small number of affected users; we'll be monitoring to see if changes need to be made to the queue to prevent this duplication from occurring.

  • Sounds like this is a no, but will there be any restrictions right away to prevent duplication, such as "If the post is closed as a result of the flag (and subsequently reopened)", "if your flag is rejected", or "only if the flag is still active". Or will these be the types of things you are monitoring for? Aug 6, 2014 at 8:19
  • We'll keep an eye on this, @psubsee2003, but keep in mind that this is not particularly easy to abuse as you have to change your privilege level in order to do so. We may also start aging close flags in the future, which would tend to increase the chance that a given flag gets ignored and you have to earn 3K to get attention.
    – Shog9
    Aug 6, 2014 at 17:12

You must log in to answer this question.

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