I was previously using this bug to my advantage, but now I'm being honest and reporting it. Anyway, normally, when you flag an answer as "not an answer" using the standard option and you have already flagged it as such (and the previous flag has been dismissed with a status),

enter image description here

you receive an error message:

enter image description here

However, you can flag it as not an answer again using the manual entry box:

enter image description here

...and the system will treat it as a normal not an answer flag, even though I have already flagged it previously as such. The proof:

enter image description here

This seemingly incorrect behavior should be replaced with one of the following:

  • Treat it as a custom flag, which it appears to be.
  • Reject the flag and complain that it has already been flagged as not an answer.

Anyway, it's a bug, and it could be used to one's advantage (keep flagging until it is deleted), and it should be fixed.

  • 1
    The only thing this accomplishes is your account being prevented from having this ability or worst the closure of your account
    – Ramhound
    Commented Feb 14, 2014 at 0:42
  • [status-completed] ... Details please? Commented Jan 19, 2019 at 2:38
  • @TwistyImpersonator Typing "not an answer" into the custom flag field on a post where one has already cast a standard NAA flag will give an error message instead of allowing one to submit a second NAA flag.
    – gparyani
    Commented Jan 19, 2019 at 9:01

1 Answer 1


I'm not sure if it's a bug. the previous flags are dismissed and you're flagging it for some other reason, perhaps the post has been vandalized again. It's up to you to not flag it multiple times.

And oh, don't be fooled thinking Mods don't notice this or others haven't tried this before. Frivolous flags are treated with disdain, and not only we decide to not take your flags seriously, the system will learn the same. Don't do it.

  • Yes, but see this Meta.SO post. They are normal NAA flags.
    – gparyani
    Commented Feb 13, 2014 at 19:58
  • 2
    It's a bug for two reasons: 1) these flags get converted to a different type, which changes how they're processed... and 2) that change in type circumvents the normal checks that prevent the exact same flag from being raised multiple times.
    – Shog9
    Commented Dec 13, 2014 at 0:17

You must log in to answer this question.

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