When working with the 10k moderator tools, the "to handle by you"-flag count on the sidebar at the right should be decreased after handling flags. At least, that's what it did before the update the rolled out the new close reasons (i noticed the style also changed a bit).  Before, I would handle let's say five "not an answer"-flags. If I'd reload the site, the handled questions would be gone and the count (given that no new flags arrived) had decreased.  Now, after handling flags and reloading, the questions are still gone, but the count isn't decreased.  Also, when I handled all flags in a certain category, it's link should be gone from the sidebar. Instead, I get the link, the old count and when I click it, there are no questions on the page.
9082
It looks as if the 10k-tools flagged post list is b0rken.  Next to the review link in the toolbar there is a flag counter showing there are 10 flags to be reviewed:    Clicking on that flag counter leads to an empty page:        The moment I visit that page (through clicking on the flags counter, or by going to the review queue first then clicking on Tools, selecting the flags tab if not already selected), the flags counter disappears from the toolbar:    but after a while (half an hour, an hour?) the flag count re-appears in the toolbar.  Either the counter is wrong (presumably taken from a Redis cache somewhere) or the 10k flag review page is falling over every time someone tries to load it.  This at first appeared to happen only on Meta, on Stack Overflow the flags page has plenty to review. However, there are now  on Stack Overflow.
49163
With the ever-growing network of Stack Exchange sites as well as the increased traffic and therefore larger number of moderators, the way policy updates and feature changes are currently announced makes it almost impossible for moderators to catch up. Currently, if you as a moderator want to be up to date on what's happening, you have to:  Hang around on Teacher's Lounge all day and be sure to check the starred or pinned messages Visit Meta Stack Overflow and look at the recent feature changes as well as the top questions for the last week or months Wait a few weeks until you receive a newsletter, which only covers the major issues  What you could be missing… This is a process that needs moderators to actively check for any new info. For example, two things I completely missed as a moderator unless some others had informed me:   – I've always been strict about quality flags but it took me a while to see this topic. I just had a talk with @ChrisF yesterday who apparently hadn't seen the topic until now. No offense, but if you want moderators to act consistently, you have to get this information out more reliably. There are new ways for moderators to check review statistics. Those are buried somewhere in a list of links. Unless you check out that page (which I don't do that often), you just won't find these links. The rationale can't be that &quot;you'll find this out when you see it, and then play around with it&quot; – why make these tools in the first place if they shouldn't be used right away?  Now, I can imagine that – even on the larger sites – there are moderators who simply cannot afford to spend the entire day in chat, or even on Meta. Moderating is something most of us to &quot;just for fun&quot;, and often while working. … and why that's bad? But yet, we moderators are the first port of call for support on our sites. You wouldn't want the site mods to respond &quot;Umm, no idea, they must've changed that recently.&quot; And you want them to act consistently (e.g., with regard to the low quality flags). I dare say that if an otherwise very active moderator isn't there for two weeks, they'd miss out on important (policy/feature) changes. A new information feed What I propose is that Stack Exchange actively pushes out small bits of information to all moderators of all sites. Unlike the newsletter, which is only sent every few months, these messages could be kept really short and to the point. In the mod page, you could make a counter for updates:  And there, list all the new stuff, for moderators to read:  You could then just write a small message:  Be more strict on very low quality flags If a very low quality flag doesn't exactly apply, consider declining it with an appropriate message. This is to ensure that validated flags are accurate. See more:   And done. Now you get the information out to every moderator, in a feed that now pushes out the important bits instead of waiting for moderators to find them. This would ensure that moderators who can't check in every day still get news of the critical feature and policy changes, which results in a more consistent moderation experience for the users, and in the end it might also save the team from repeated questions about new features or policies.
51512
I just flagged a comment as "obsolete" in . To my surprise, it was deleted immediately, just after pressing "Flag Comment".  Now I see it in my flag summary as helpful:        Does this mean that obsolete flags are somehow handled automatically? I went through  but could not find any description on this.
41802
I'm not quite sure what to search for on this, but I noticed a little number on one (and only one, so I couldn't pinpoint a trend) of my flags in my flag history.   The text appears as follows:     title of question [closed] (1)   the flag was marked as helpful, the question was subsequently closed, yet a little (1) remains. I tried to see what that question had that the other questions did not, but moderator shut-down, specific tags, number of votes didn't matter. My only guess would be number of answers to the question? But I have no evidence for that. Does anyone know for certain?
110697
Can we implement the low quality flag to be like the abuse or spam flags. So if a certain number of low quality flags are made  on a post (whether it be a questions or an answer) the post is deleted?  This would also relieve *close vote and delete vote queues. *which is a much discussed topic.        related:
64271
When looking at my flag-responses page, it's not always easy to tell what's new.  Sometimes flags take a while to resolve, so I might have one farther down the page that only now got resolved.  Moderators have always been able to leave messages for declined flags and now can leave them for helpful flags too.  If the moderators took the time to write them, we should try to read them.  But right now all I can do is scan the page and see if anything new jumps out at me.  For other types of responses (comments, edits, reputation changes, even changes in favorites), the new information is highlighted through styling (background color).  Could we do something like that for the flags page too?  Or provide some other way for users to see their newly-handled flags?
44468
On beta sites, when a post gets closed without comment, Community ♦ flags it for moderator attention.   Apparently, a comment entered through the freeform close reason doesn't count:    As you can clearly see, there should be no doubt that a comment already exists on the post  Could this be fixed? I don't think it's that important -- I just have to decline the flag, however on larger sites this may lead to a lot of extra flags.
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
84435
It's recently been mentioned in some chat conversations that low-reputation close flags are given too high an importance for moderators and should be directed to the community instead. It's been suggested that on Stack Overflow, close flags should go to the 10k queue rather than the mod queue (this may in fact already be implemented).  While I don't entirely disagree with this, I think it only speaks to one head of a two-headed problem. The more pressing issue - especially on Stack Exchange sites, as opposed to the trilogy - is that close votes don't reach the moderators often enough.  On a site like Programmers.SE, for instance, where there are still a lot of historical questions that need to be cleaned up or closed - it's almost pointless to cast a close vote because no one will ever see it. Better to just flag for moderator attention and not waste your vote (and get some of those lovely flag weight points while you're at it).  One suggestion was to have the first close vote on a question automatically generate a mod flag. This was fairly criticized as creating more work where there should be less.  However, the basic principle of the idea makes sense; diamond moderators and privileged users should have some way to be aware of new close votes, just in case the rest of community isn't pulling its weight.  So a better (IMO) proposal is to turf the near-useless "10k tools" close/delete pages and integrate their content into /review. This would give moderators (as well as privileged users) the ability to review close votes, on sites that need it (such as P.SE), without forcing them into an unwanted workflow on sites that don't (such as Stack Overflow). This also has the advantages of:   Showing an excerpt and tags along with the question titles; Reducing overall clutter (the 10k page is pretty noisy with all its sections); Displaying many more questions at once (/tools seems to have a max of 30, expanded); Giving a realistic indication of how much material there actually is to get through; Embedding action links (e.g. flag/close/delete); Seamless integration of close votes and close flags in a meaningful area; Generally giving reviewers the feeling that they're actually making progress.   It would also be incredibly useful if moderators in particular could dismiss questions from the closed/deleted review just like they can dismiss flags, in effect saying "I don't care, let the community handle this one."  Questions would appear in the closed/deleted review page after the first close vote occurs, and then sorted either by the time of that vote or by the total number of votes (or both). Dismissing (if implemented) would dismiss it permanently, ignoring any new votes, until the question is closed or reopened. Straightforward process with minimal noise.  Bottom line: I think that the /review pages encapsulate a pretty good workflow, and it's a shame that critically-important information is still being jammed into the old /tools clunker when we already have something so much better. My responsibilities as a moderator and/or a 10k user would be a whole lot easier if I could review close and delete votes through /review.
64818
Previous posts                  As of today, the Moderator Flag Dashboard is officially graduated and the old version sent to the smelter's yard.  Based on stats from the past month, virtually all moderators were already on the new UI (thank you) so you hopefully won't notice any change.  That said, I would like to highlight the handful of improvements we made over the last month and a half based on your feedback:   A more responsive navigation bar at the top of moderator pages, improving the mobile experience. Similarly, , increasing room on the screen for the first question. . .  Not only do the headers look better, they now function better.  Now you scroll to and highlight the post/comment each time you click the link, not just the first time. .  Posts by the same user are grouped together and ordered newest first. .  We eliminated the VLQ (auto) side effect so now "Resolve all flags (auto)" doesn't do anything surprising.  If you still want to leave a comment or decline, you can do so with the buttons next to the individual flags.   Bugs and Feature Requests  Since this project is officially launched, all bugs and feature requests should be done in the form of questions tagged  on MSE, not answers on this post.  Feel free to post an answer here if you have specific concerns about the release process.
99517
In , can we indicate alongside each flag in the mod dashboard if the post that was flagged has been edited or not? Something like a simple  N x Edits since flagging.   This way, moderators will be reminded that they might have to check the revision history to grok the reason for the flag. Note that this is different from , which requested that the moderators be shown the original version of the post. The response has been overwhelmingly negative, and rightly so.   My request would merely require a simple check to see if any edits have been made since the flag was raised and a short notice. The view that the moderators get should still be the current version.
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.
66080
Every once in a while I take a look at the tools page and see a high number of flags - like right now.  And there is indeed some pretty spammy stuff in there.  It's fairly self-evident what to do with flagged questions, I think - just vote to close/delete if the flags are in fact accurate.  But what about flagged answers?  It doesn't really seem like there's much we can do about those.  Should we:   Flag them again, hoping to bump the answer down and/or get it auto-deleted? Flag for (real) moderator attention, i.e. to confirm "yes this is really spam"? Just leave them alone (assuming that a proper mod will find it soon)?   Also - is there any particular action we should be taking if a post is erroneously flagged - i.e. somebody got annoyed that a question wasn't marked CW?  Some guidelines on how best to use this feature would be appreciated.
2762
The Problem  Currently if I flag a post, I cannot check the status of the flag unless I have prior helpful flags. This means, for example, that a new user who wants to check the status of his first flag cannot do so while it is pending (active).  This feature request is based on my experience on MSO, where I wanted to check the status of my flag but could not get to the summary page without cheating (tweaking my SO link to work with MSO). It also stems from this question, where the OP indicates he had the same issue:   My Proposal  If I have flagged any post, then show me a "flags" link (red arrow in image below). If I have any helpful flags, then the number of helpful flags should be displayed (blue arrow). If I have not flagged anything, then neither should be displayed (as with current site functionality).
46116
Are moderator tools, specifically flagging or voting to close going to be implemented in the Android app? If we have a dispute, we should at least have the flag option.  What about share option? If we would like to share a question, we could long press on the question title, and the question title, excerpt, and short URL copied to clipboard.
1783
Here is the close queue:        Here is an active flag I have:        I currently have 5 flags pending in the close queue. Some, like this one, are months old. This doesn't feel right and may discourage newer users from flagging things that need attention with the assumption that a flag may be ignored for 4 months, so why bother?  Here are some possibilities:   Bump flags that have been languishing for more than 30 days to the front of the close queue (or weight questions with said flags a bit higher). Won't solve the issue, but will make it less egregious Punishing a misbehaving mod by forcing them to go through every sub-3000 user's flagged close votes in the queue and free them from flag limbo , "a new 10K flag list for "stuck" flags, which would be any close flag that is unhandled within 30 days."   This question has been heavily edited under the assumption that flags didn't get refreshed every day. Apparently they do, thanks to Bill and Asheesh, so sorry about the misdirection. Languishing flags still an issue though!
72270
Sometimes when in the middle of writing a custom moderator flag, I click outside the flag dialog, for example because I want to get a link to one of the answers. This closes the flag dialog and forces me to write my message all over again, which is rather annoying. Therefore, I propose that clicking outside the flag dialog don't close it when I'm in the middle of typing something in a textbox (a&nbsp;custom moderator flag, a custom close reason, etc.).