Yes, this is an old issue.

First reported to QA Jun 2012. We could only repro in our QA environment when simulating latency.

I hate how often we give this answer out, but it appears to be lag. We are working with the developer to resolve all report latency issues.