Board Thread:Newbie Questions/@comment-24983865-20140525174012/@comment-25030726-20140606121444

I have observed behaviour similar to this. From what I can tell, it is simply an issue caused by the fact the application buffers a number of events and then writes them all to the database at once. This makes sense since the application has to get a lock on the database to preserve data integrity and there is no way for all players' instances of the game to have a lock on the database at the same time. So, what happens is that your instance of the game will buffer a number of events, then get a lock on the database, write those events to the database, and then give up its lock on the database so that the next player's game instance can write its actions to the database. There really is no way for Social Point to fix this because it is a limitation of the technology rather than an actual bug. The only way to overcome this is to keep this in mind and give your game instance some time to get a lock on the database and perform its write operations. So, simply waiting a minute after important events before exiting the game will give the game time to record your latest important events - and it should only take a minute at the most because database transactions are extremely fast.

I do web development for a living.