I flagged this question almost a week ago now, and the flag is still waiting for review (it shows as "waiting for review" in my flagging history)

My flagging history stats

The flag in question

Is there anything I need to do to get this handled faster? Did the flag get lost somehow?

The question originally had only a couple obscure tags on it, so I thought that might have been the problem - but I edited it a couple days ago to add the and tags, and that doesn't seem to have helped.

  • 1
    Is it showing waiting for review in your flagging history? – Azik Jul 2 '13 at 7:15
  • @Azik Yes. I've updated the question to make that clearer. – jcsanyi Jul 2 '13 at 7:17
  • 1
    The unicorns were ordered by BoltClock to burn it because your flag weight is the same as that of a duck – Cole Johnson Jul 2 '13 at 7:19
  • Did you choose "Other" when flagging? – Shadow Wizard is Vaccinating Jul 2 '13 at 7:46
  • @ShaWizDowArd No, I flagged it as "unclear what you're asking" - you can see it in the image above. I've flagged at least one other question the same way, with no problems. – jcsanyi Jul 2 '13 at 7:49
  • Hmm.. maybe it got disputed by reviewers then and due to some bug not showing as such. Well, we need to wait for a mod to check it anyway. – Shadow Wizard is Vaccinating Jul 2 '13 at 7:54

No, it's not technically lost, but flags to close a question are no longer shown in the moderator only queue. Thus, it needs others that have closing privileges to act on it. Your flags were acted upon faster in the past because the diamond moderators serviced them in turn, but they should only be handling exceptional cases, not simply questions that haven't gotten enough velocity to close.

Keep flagging as you see stuff that you think needs closing, don't worry too much about what happens to it after that - beyond of course making sure that you're flagging appropriately.

  • 4
    "no longer shown in the moderator only queue" - that's a major change, was it announced somewhere? – Shadow Wizard is Vaccinating Jul 2 '13 at 13:32
  • @ShaWizDowArd Well, if not it's announce now :) I believe it was mentioned in a few places as part of the larger changes we've been rolling out, but I don't think an individual post was written just to go over it. – Tim Post Jul 2 '13 at 13:36
  • 2
    @TimPost It was mentioned that flags now result in the question being put in the close vote queue, I don't think it was mentioned that it no longer shows up in the moderator queue as well. I was under the impression that at least for some period of time they went into both queues. – Servy Jul 2 '13 at 13:49
  • Nothing about it in the blog post. – Shadow Wizard is Vaccinating Jul 2 '13 at 13:50
  • We've repeatedly said we were gonna do this since the new review queues were introduced... It just took a while, @ShaWizDowArd – Shog9 Jul 2 '13 at 15:10
  • @Shog9 fair enough. So suppose I flag for closure and see it's still not closed week/month/year later, how to "bump" the flag as I can assume for sure it's lost among the 50,000 other flags? (speaking from the point of view of <3K user) – Shadow Wizard is Vaccinating Jul 2 '13 at 15:12
  • 1
    @Sha: that's hard to answer in the general case; how important is it that the question be closed? The easy answer is: get 3K, vote on it. Another option would be going back and custom flagging it, but this rather defeats the purpose unless someone is dying. – Shog9 Jul 2 '13 at 15:23
  • 1
    @Shog9 I think this will lead to much less questions getting closed; how good or bad this is I can't really say though. Only time will tell! – Shadow Wizard is Vaccinating Jul 2 '13 at 15:25
  • That's something I'm keeping a sharp eye on, @Sha – Shog9 Jul 2 '13 at 16:01
  • @TimPost thanks for the explanation, but that still doesn't entirely explain this, because it's not just older flags that were acted on faster. I've raised over 20 flags since this one, and they've all been handled in a couple hours or so. – jcsanyi Jul 2 '13 at 19:21
  • I'm not overly concerned about this post. Certainly nothing that warrants a custom flag or anything. I was just checking on my previous flags to ensure I'm on the right track with my flagging, and I noticed this one. It still looks (to me anyways) like some sort of a bug - unless it's just a combination of the bad tags leaving it ignored for a couple days, and then now that it's older it gets pushed down in the queue backlog and even the good tags aren't enough to get it pulled out? – jcsanyi Jul 2 '13 at 19:23
  • @Shog9 Are flags to close still shown in the 10k tools? – hichris123 Jan 4 '14 at 20:54
  • No, @hichris123 – Shog9 Jan 4 '14 at 21:00

Actually there are huge close votes review queue on Stack Overflow. Your flag is one of them. And all close votes question comes in random order. That's the reason why your flag is not handled yet.

Wait and hope for the best.

  • Then why would all my other flags have been addressed in no more than a day or so at the most? I understand reviewers often filter the close-vote queue by tag, but shouldn't my adding the extra tags have helped if that was the problem? Is the queue working with a snapshot of the tags that perhaps doesn't get updated when new tags are added? – jcsanyi Jul 2 '13 at 8:21
  • Because other users closed your previously flagged questions direct from the post page. I can guess it. – Himanshu Jansari Jul 2 '13 at 8:27
  • 1
    Most of the review queues don't have an entirely random order. They are biased to return more recent items over older items, although there is still some randomness applied so that multiple people aren't always reviewing the same item. The post you linked to is from the old review system and is no longer relevant. – Servy Jul 2 '13 at 13:51

You must log in to answer this question.

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