Yes, yes, yes, I have seen , but it doesn't seem to be the case for me. marking it as dupe because @Animuson .  I am getting this message when I click flag on Stack Overflow:        However, my last declined flag is from feb 28 - a month has passed already. Since that moment I had 32 helpful flags, 5 aged away, and 3 pending - and no declined.  What's the reason behind this notice being shown for me?
123404
I am seeing the warning that "Some of your recent flags have been declined." on Stack Overflow.  However, looking at my flag history, this is how it is laid out:  38 Flags overall   7 Active Flags 1 Declined yesterday 1 Declined 2 days ago 1 Declined on Jan 23rd 1 Disputed on Feb 18th 27 Helpful since Jul 19, 2013   Do 2 declined flags within 2 days really trigger this warning? It seems like if I had a larger string of declined flags that this would trigger it, but 2 in a row shouldn't trigger it IMHO.
118532
Just browsing and came across , but the post notice doesn't have a link to the duplicate:
11698
I noticed that on both sites where I am a moderator the flag counter is occasionally not showing any flags even when there are flags in the queue. A refresh of the page leads to the correct flag count to be displayed. I noticed this happening when I visited the site for the first time in a few hours, when I was recently active on the site the counter seems to stay accurate.
77316
So there's a feature request (I'm not the OP) which has recently been tagged status-declined.  I was/am highly in favor of the request.  Now I'm depressed.  I will probably drown my sorrows tonight in a case of dark English ale (nothing like the old world).  This particular feature-request had 72 upvotes on it and the reason given for declining was not all that great (IMHO).  How long do we wait (realistically) before asking for a highly-popular feature request which was declined to be reconsidered?  (ok, to save you some forensic time the feature in question is , but this is really just in general)
104229
I flagged something as spam, then was only 90% sure I'd done so, so I clicked the flag link again to check. It showed me this:    I had, of course, only raised the spam flag, not the offensive/abusive/hate flag, so the latter probably shouldn't be saying I did.    Ah, this may be a duplicate, I didn't search enough:        And if so, it's been around a while.
17713
I checked my  to see whether I can find something similar to the main-site flag-history for chat-flags, but didn't find anything. I recently had the (dis)pleasure of regularly having to deal with a user, that has been deleted multiple times. Whenever they show up (with the same nick-name) again I have to flag them again. I'd like to get an overview of how often I had to do that, and whether my flags were helpful for the moderators. As such I propose the implementation of a flag-history as it is already in place for the main-site for chat-flags, that request moderator intervention. To be completely clear I am not talking about the 10k user flags, which are acted on in a matter of sometimes seconds with instantly visible results, but about moderator attention flags from this menu:
80643
I know how disputed flags work. Today, I reviewed a "not an answer" flag and marked it as invalid.   I've later seen a disputed message with this reason:     invalid flag         disputed - a moderator reviewed your flag, but found no evidence to   support it   Given that disputed flags are in the ,  Is this message applicable only to my flag or is this message also for the original flagger?  Or put otherwise, are all disputed flags now shown this message (or similar decline reason)?  I've run out of flags for today to test this further.
36840
The flag queue lists automatically-detected .  According to  and other questions on MSO, there is nothing wrong with such duplicate answers&mdash;except insofar as they are potentially indicative of a duplicate question.  So, having verified that the answers do not merit a flag for any other reason (and having flagged the questions as duplicates if appropriate: although if that was the purpose of this exercise, shouldn't the system have raised automatic flags on the questions instead?), how should one respond to these flags?  It seems that the only option is to flag for moderator attention, either:   because "I do not agree with the existing flags on this answer, they are incorrect and should be ignored." (invalid flag), even though I do agree that the answers are indeed duplicates; or for a custom reason.   Neither of the above really feel very appropriate.  Perhaps if the flag was instead "suspected spam" (or similar) it would be easier to flag as being invalid?
19242
I flagged a post today, typed out a fairly thorough explanation, clicked the button... and got told that I'd already flagged this post (for something else, which I'd forgotten about) so this flag wasn't allowed.  (This happens if the first flag is still active.)  The dialogue with my explanation was gone at this point, so if I wanted to communicate with the moderators about that, I was going to have to start over.  (In case you're wondering how this could happen, one flag was related to the post itself and one was related to the user -- there being no way to flag a user directly, you have to hang it off of a post.  But I've also seen this with cases where the first flag hangs around unhandled for a week or two and I've forgotten about it.)  Since the system is going to detect that I've already flagged a post and reject a second flag, can it do that after I click the "flag" link instead of waiting until the end of the process?  (Or gray out the link so I can't click it in the first place?)  2015-12-18: someone suggested to me in chat today that this had been implemented, so I tested again.  The behavior has not changed: I flagged a post using "other", then flagged it again (also "other") before the first flag was handled, and the flag was rejected only after I'd typed the message.  (I did this on a site where I'm a moderator so I could then clean up after myself.)
17867
My reputation on Stack Overflow suddenly raised from 35k to 45k! And it seems that on other sites as well! It must have been in the past hour!  What happened? I don't see any record in the reputation history or jump in the chart, everything is just smooth! And it seems it happened on other sites as well!  I'm not complaining, just curious! :-)  EDIT: The discussion was "it was in the banner, you should have read it", and when I replied that I am closing banners without reading, and important announcements like that should be in the notification box, I got comments like "Oh yeah not reading banners is bad".  Now look at this and tell me: is anyone still surprised that I got used to closing banners without reading?? ;-)
95825
I've noticed that with the new question asking form, sometimes, attempting to submit a question will post two identical copies of the same question.  I've  (), but at the time, I assumed it was just a temporary fluke. As far as I remember, I just reviewed the question, saw no errors, and submitted it. (That's all the info I have.)  However, I just saw this happen to someone else, so it can't just be a fluke on my end. , and . The author claims there that they did indeed double click the "Review" button, but their question didn't go through since it didn't have a required tag, but when they tried to submit the question with the required tag, they only clicked it once.  Also, now that I think about it, it could not have been just a temporary client-side issue on both our ends. The system is supposed to  if one tries to post more than one question in 30 seconds. Neither of us got a CAPTCHA. This means that the server accepted the double post, and so it's a server issue.  This has the effect of denying users badges that they would have otherwise qualified for, since a single negatively-received, closed, or deleted question . This means that even if the double post is deleted and the original is upvoted, the user won't qualify for that day since they've made a "bad" question on that day. (While they may be able to later reverse this 60 days later by undeleting and re-deleting their question - questions deleted more than 60 days later aren't considered "deleted" for the check - they often won't be able to, since most of the time, users will have downvoted the double post, which also disqualifies one from the badges.)  Can an employee go through server logs to see what happened in both these cases, and add some safeguards to prevent accidental double submissions of questions? This seems to have come up when the new asking form was deployed.  Update: There was another case just now:  was . As both have the exact same time of submission, this is an instance of this bug, since as I said above, this thing is ordinarily prevented by a CAPTCHA.
82024
A few hours ago, I flagged  as not an answer. Additionally, I left a comment, basically saying that this answer has nothing to do with the question.  My flag got declined with the following reason:     flags should not be used to indicate technical inaccuracies, or an altogether wrong answer.   However, when flagging as not an answer, the following description is displayed (emphasis mine):     This was posted as an answer, but it does not answer the question. It should possibly be an edit, a comment, another question, or deleted altogether.   &lt;rant&gt; Basically, I am a bit wary about this declined flag right now, because it matches the description on what should be flagged as an answer and with my current flag weight, this declined flag destroyed about two days worth of flagging. That just took all the fun out of it for me, especially, because I am a responsible flagger, and open the questions to really read them and the answer if I am unsure - even if the answer already has several flags. &lt;/rant&gt;  So, what am I asking... Well: Was it correct to decline my flag? If so, please fix the description of that flag option. If it was not correct, how can we prevent such "false flag declines" in the future?  Especially in the context of high flag weights where one declined flag really hurts.  UPDATE:    And another one!!   I didn't even flag as not an answer, but as "Other". My comment was: "Although this is the accepted answer it doesn't help. See comments for more info, basically: Contains not much more than a dead link." It is common sense to flag answers that contain only links, even more so, if the link is dead. As this was an old accepted answer, downvoting didn't help, because I still couldn't delete it. And my flag didn't even ask for deletion, but for "Mod attention", whatever that might be.  You just lost an active flagger, because every dismissed flag costs the equivalent of 50 to 100 "helpful" flags at my current flag weight. All because of some arbitrary decision from some anonymous mod? That just sucks and shows how little the honest flagging effort is honored.
27413
I have flagged the following question as a duplicate.    Now I want to know: after how long time will it be stated as active?  I do not have problem with anything here. I just want to know after how long time the request (of a duplicate question) will automatically be rejected or approved.  OK, I got the things, so it will remain active until moderators will have a look at it...  But don't you think we should have a limit that after a certain number of days this kind of request will be dropped (or cancelled)?
90989
What should we do with Stack Overflow-specific questions on Meta Stack Exchange?  .  , as long as it meets some (underspecified) conditions.  Whose advice should we follow?  If it's Tim's advice, what exactly are the conditions for flagging (preferably in quantifiable terms - not sure what "undecided" means)?  If we shouldn't flag them, or just some of them, what should we do with them then (or the rest of them)?  Should we close (and eventually delete) them all?  Note - by "flag", I'm exclusively referring to flagging for migration.  My opinions:   In the case of completed requests, isn't it worth keeping them around for the sake of reference? And if we're going to keep them around, shouldn't it be on the correct site? In the case of uncompleted requests, if we close and/or delete these, why do so, just to have them show up on Meta Stack Overflow some point down the line (minus all the discussion and votes should approval / disapproval)? And is there really such a big difference between something posted on 15 April (pre-split) versus something posted on 20 April (post-split)? Why treat them so differently? Isn't that just us being blinded by the rules? Or is migrating them really such a massive deal?
102603
I have been going through some old posts, flagging them as necessary. But I have noticed that the number of posts that I am able to flag is continually staying at ten. It seems that the new flagging system has messed this up.  I am able to keep flagging posts even after 10, so I know it isn't a UI bug. This is a very big problem, because I can flag infinitely many times. And I am pretty sure this isn't the intended behavior of the overlords This isn't because I am being awarded more flags. I flag more than 13 posts in 5 minutes, and I can keep going without restriction  Some of the flags were accepted, so now my number is up to 13. But it is still staying at 13
120963
If Community ♦ flags something for low quality or because of consecutive closed questions or whatever, I always have to click that the flag was helpful (or declined):      To my understanding, it doesn't make a difference. So, why ask in the first place?
98487
Today I clicked on Review and saw the message below.     You've failed too many recent review audits - looks like you might need a break. Come back in in 7 days and try again.   Why does this type of message appear?  Is there any daily limit to viewing reviews on Stack Overflow?