What is meta? ×
Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 128 Stack Exchange communities.

I flagged a post yesterday as a duplicated question and now its status is set to eventinvalidated. I can see this in my Flagging History section.

I'm not sure I understand what it means since the post is still there and has not been deleted. It's the first time I have seen this status.

Could someone enlighten me about that?

enter image description here

share|improve this question
    
What status where? –  Undo Jul 5 '13 at 14:52
    
Screenshot please? –  Danny Beckett Jul 5 '13 at 14:53
    
@Undo Updated, it's in my Flagging History Section. –  ForceMagic Jul 5 '13 at 14:53
    
@DannyBeckett I added the picture. –  ForceMagic Jul 5 '13 at 14:55
2  
Not exactly marking as dup in chronological order, my apologies for that - I answered the same question just asked a few moments ago without realizing that this one existed. –  Tim Post Sep 3 '13 at 11:13
    
@TimPost Hmm can't you revert it? and do it the other way around? –  ForceMagic Sep 3 '13 at 13:11
1  
@ForceMagic Duh, I could have, you know, just merged it, which I just did - sorry about that! –  Tim Post Sep 3 '13 at 14:04
1  
@TimPost Awesome Tim! :D thanks a lot :) –  ForceMagic Sep 3 '13 at 14:09
    
@TimPost I have seen this other question before posting mine but didn't know if it was necessary to explain the reason of this status, so post another question. If mine needs to be removed, let me know :) –  Chris Sep 3 '13 at 14:41
    
@ForceMagic Apologize for this, everything is back to normal now :) –  Chris Sep 3 '13 at 14:48
    
@Chris No, it will just lead to this one, I completely botched the dup process on this one. My bad. –  Tim Post Sep 3 '13 at 14:58
add comment

1 Answer 1

up vote 12 down vote accepted

The flag was invalidated, but not declined, it doesn't count against you. This particular flag result reason exists because:

  • All flags are kept in the system, even ones that are impossible to resolve or act upon (we don't hard delete much of anything here)
  • The system needs to be able to resolve them when impossible scenarios (like the target duplicate being deleted) happen.

If this weren't the case, we'd have the following options:

  1. Automatically mark the flag as helpful (bad, as many flags aren't helpful)
  2. Just delete the flag (bad, as people would wonder where their flag went)
  3. Nullify the flag like this, in a way that doesn't count for or against you

It's not anything you need to worry about. It's just a plug that fills a gap when a scenario sets up that makes your flag impossible to resolve as helpful or unhelpful. The flag is in its final state - it's not lingering, it's fully resolved. We should make this more obvious on the flag summary.

share|improve this answer
1  
Also, is such a flag counted as "disputed"? If not then which of the counters? –  Shadow Wizard Sep 3 '13 at 11:11
1  
@ShaWizDowArd No - It's just nullified. It's in the system to remain in your history but is neither helpful, disputed, or unhelpful (declined), those are three totally different resolution types in the DB. Think of it like garbage collection (not to imply the flag was garbage, more the principle). –  Tim Post Sep 3 '13 at 11:14
    
Fair enough, just nitpicking now - why not add "X invalidated" below "moderator attention flags", same way there is count for everything else? :) –  Shadow Wizard Sep 3 '13 at 11:20
3  
@ShaWizDowArd because that isn't nearly cryptic enough and I value my job security. –  Tim Post Sep 3 '13 at 11:21
1  
Thank you very much for that clarification. Correct me if I am wrong but I think I have now understood why I can also see on my flag history page *older flags were not recorded helpful/declined –  Chris Sep 3 '13 at 12:22
add comment

You must log in to answer this question.

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