cdent has written a good summary of the issues asynchronous operations in TiddlyWiki: DesigningForAsynchrony
The core problem is that in some situations the client will attempt to repeatedly save the same tiddler, without waiting for previous save operations on the same tiddler to complete.
I agree with cdent that this is likely to require significant rework of the synchronisation and adaptor subsystem in the client. Because that is a large undertaking, I agree that in the meantime we should alter Cecily/preso so that they don't autosave the map, but rather require a manual step to save it.
The core problem is that in some situations the client will attempt to repeatedly save the same tiddler, without waiting for previous save operations on the same tiddler to complete.
I agree with cdent that this is likely to require significant rework of the synchronisation and adaptor subsystem in the client. Because that is a large undertaking, I agree that in the meantime we should alter Cecily/preso so that they don't autosave the map, but rather require a manual step to save it.