We had an issue with one of our reports showing results that are exactly 3x larger than they should have been. the data was fetched from SPICE dataset that is automatically refreshed EOM. Forcing manual refresh seems to have fixed the problem.
Based on further investigation - it seems that it was some sort of a bug in Analysis and Manual Refresh have forced re-calculation. The week before someone else pulled numbers (which was after auto refresh) and saw correct numbers. This week different people opened report and saw wrong numbers. The discovery was done by chance because we had backup of previous months data and compared results from the report to those numbers.
Is this a know bug? It is disturbing for stakeholders to get wrong numbers and then try to charge clients based on those wrong numbers (we use report for API overage use chargers).
The number of rows did not change - manual refresh fetched same-ish (manual refresh fetched few more rows to account for extra few days after start of the month) number of rows as did automatic refresh (both were full refreshes). But the number in UI was 3x larger before manual refresh was triggered.
Hi @max.bondarenko
Thank you for letting us know. I would recommend filing a case with AWS Support where we can dive into the details so that we can help you further. Here are the steps to open a support case. If your company has someone who manages your AWS account, you might not have direct access to AWS Support and will need to raise an internal ticket to your IT team or whomever manages your AWS account. They should be able to open an AWS Support case on your behalf. Hope this helps!