Fixed in the next release. If the view tally job was run while debug/development mode was active, an undefined index caused the process to abort. This left job entries that were marked in process, so subsequent attempts to tally views would always be skipped. It is possible that views would get rebuilt immediately following the next VaultWiki upgrade, and only at such times.
The undefined index which was causing the problem has been fixed in the next release. Additionally, any open related job entries are automatically closed by upgrading to the next version. In case a similar problem happens in the future, beginning with the next release, we ignore an open tally if it is more than a week old.