CloudWatch sensitive data count is not refreshed on the other user account

We applied Data Protection Policy on a log group. Then we found that it detected some sensitive data included in some logs. (20 items in the picture below)

So we deleted the logs that included the sensitive data. But when we checked it from the OTHER user account, it didn't show the corrected number of sensitive data (still seeing 20 items in the AWS console).

It seems that if you push the "reset alert" button on the top of the UI, it refreshes the number of the sensitive data, but the refresh doesn't look applied when you check it on the other user account (it still shows the old number of sensitive data count).

Do you know why do we see this behavior & how to apply the latest sensitive data count on EVERY user seeing the AWS console? Thank you.