What is happening is that your data change is shown optimistically on your device while your computer sends the change to our servers where its persisted into the database. Now if you navigate to another view too quickly, the new view would request data from the server earlier than the prior saving operation was finished, showing you incorrect results. In this rare case just reload the view and everything should be fine.

This is a limitation of the current system that we like to overcome in a future update.