Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

I have flagged a question saying it should be closed , but it says

declined - a moderator reviewed your flag, but found no evidence to support it

However, the question is closed as I claimed.

What's the problem?

share|improve this question
Different moderators, different interpretations. Don't worry about it. – ChrisF Jul 20 '12 at 11:27

You used a custom flag message stating:

so old question with lots of possible duplicates. should be closed

This may very well be the case, but moderators are not Google search. If, as you state, there are lots of possible duplicates which you are aware of, you could have used the "exact duplicate" moderator flag and showed us which post it was a duplicate of.

While moderators are super-human, we aren't omniscient. That said, aren't expected to know the entire breadth and width of all of the questions on Stack Overflow.

My assumption (and I am not speaking for the moderator here, it wasn't me though) is that you only pointed a finger without any evidence to support the claim. With other flags (OT, NC, NARQ) the post itself is the evidence, but in the case of duplicates, we need something more than "a duplicate exists", tell us what it's a duplicate of.

However, the question is closed as NARQ. Without knowing what exactly the question was a dupe of, looking at the question on its own, it's obvious that it is not a good fit for Stack Overflow in it's current form, so I assume it was closed on those grounds.

As a general guideline, if a flag leads to action on a post, the flag should generally be marked as "helpful" even if the flag doesn't align exactly with the action taken; the general idea being that you alerted us to something that was wrong, and it was indeed, helpful.

However, sometimes, moderators are flooded with similar flags from the same user (I'm not sure if this is what happened here) and we will decline a few of them to indicate that the close reason isn't correct.

This is acceptable, in that if a user is going to be very active about flagging, but isn't flagging the content correctly, it helps make the entire process more efficient if the flags that are given are generally more in line with what's actually wrong with the post.

Then, when the user gets the decline and reads the message, they generally flag more appropriately, and it streamlines the entire process for both sides.

share|improve this answer
Great explanation. That also explains why a handful of my NAA flags on link-only answers were recently declined .... (inaudible mumbling about invisible flag weight). It has certainly made me pay more attention to what I flag. – Shawn Chin Jul 20 '12 at 12:28
@ShawnChin Yeah, I mean, the one-off flags we're not going to say anything about, but if the queue is flooded with flags from one user, we want to encourage that user to continue to flag (it helps the site) but at the same time, to help make it as efficient as possible. – casperOne Jul 20 '12 at 12:30

You must log in to answer this question.

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