These deposit download counts have been corrected. Typically there are a few problems every few days. However, something different happened in the past week and there were over 500 that needed correction.
The bad behavior is that a count gets reset to 0, and that count starts incrementing from there. The count correction is done by taking the starting count at the beginning of the month and adding it to the current value for any counts that are lower than the beginning month count. Not a perfect recovery in all possible cases.
The get_post_meta may be failing silently. Short term we should add diagnostics to see if the DB or cache read is getting an error.
This issue should get a development ticket to redo the count accumulation logic.
Originally from @ericknappe on this issue:
These deposit download counts have been corrected. Typically there are a few problems every few days. However, something different happened in the past week and there were over 500 that needed correction.
The bad behavior is that a count gets reset to 0, and that count starts incrementing from there. The count correction is done by taking the starting count at the beginning of the month and adding it to the current value for any counts that are lower than the beginning month count. Not a perfect recovery in all possible cases.
The get_post_meta may be failing silently. Short term we should add diagnostics to see if the DB or cache read is getting an error. This issue should get a development ticket to redo the count accumulation logic.