Unless my memory tricks me, a few days ago the % answered was around 74%, and the next it drops to 63%. Any reason why?

1 Answer 1


There was a bug in the algorithm that calculates IsAnswered. That field is used to calculate the % answered value.

The bug is now gone as of two days ago:

I've updated the query to check for nulls on the IsAnswered field - this will be deployed in the next build (rev 2014.6.16.1659, meta rev 2014.6.16.2312).

The query runs on a daily schedule, so may be a day or two before it kicks off.

(from Oded's answer)

Since this was fixed, our % answered is now... correct.

  • I assumed that the 74% was correct but using a different algorithm (since I could see the stats here didn't agree with that). Jun 18, 2014 at 14:25
  • 6
    Could also be that Nicolas and Frank ask too many too difficult questions, which confused the stats, which in turn dropped...? #D
    – Izzy Mod
    Jun 18, 2014 at 14:27
  • 4
    I want to create 50 very difficult (yet valid) questions per day, is there an app that can generate these 50 questions automatically for me? Open source, in Haskell, runs on z/OS.
    – Nicolas Raoul Mod
    Jun 25, 2014 at 6:25

You must log in to answer this question.

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