Today I've helped flag a lot of spam for this: SPAM deluge over at WebApps (and pretty much all over SE).

When I've visited my profile on WebApps to see my flag history of flag, the information about my flagging history was missing.

Note that these spam flags were my only flags on this site.

screen of my profile at webapp with missing flag history

Normally, I should have more information like when I'm looking at my Stack Overflow account.

screen of my stack overflow account with my flagging history

Is this a bug?

  • it may need a bit of time to catch up!
    – user226423
    Aug 17, 2013 at 12:34
  • This is cached too? I suppose that almost everything on Stack Exchange is cache.
    – Marc-Andre
    Aug 17, 2013 at 12:36
  • 7
    maybe it got injured in the spam-war
    – user226423
    Aug 17, 2013 at 12:37
  • 4
    I see the same thing on Gamedev and TeX, where the only flags I've ever cast are spam flags (and on TeX comment flags). So I concur with the hypothesis that the sidebar info is missing when there are 0 moderator attention flags. @Damien Here I'm pretty sure this is not caching. Aug 17, 2013 at 12:52
  • @Gilles yep, makes sense. Your and Marc-Andre's hypothesis does make sense.
    – user226423
    Aug 17, 2013 at 12:54
  • 1
    @Gilles That was my hypothesis too
    – Marc-Andre
    Aug 17, 2013 at 12:54
  • So, this appears to remain an issue in March 2014. Will it be considered status-deferred? Mar 26, 2014 at 13:56
  • 2
    I came here to post the same thing and found this post. It remains an issue. I suspect it has something to do with lack of certain kinds of other activity, and agree with Gilles' analysis. It is certainly not "caching" of any sort, it is this way on all of my 101-rep spam-flag-only site accounts and has been for a long time.
    – Jason C
    Nov 24, 2014 at 5:37
  • related (possible duplicate): If I have flagged a post, show me a “flags” link in my profile
    – gnat
    Jan 28, 2015 at 18:54
  • Issue still exists. Needs some follow up from the devs. Apr 3, 2015 at 8:22

1 Answer 1


It seems to have been fixed now:

You must log in to answer this question.

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