Highly related: short answer "no worries, the only thing affected by this bug was the finance statements".
the long answer is it didn't put it in the cashflow statement due to a typo in the command to do so, so all pages dependent on it have gotten nothing from the hourly script to tell them it's more then 0. this has been fixed. This applies to most all cashflow statement items that have been... problematic in the past few days.