I have a situation where the user creates two save conflicts without other user's involvement. One conflict is a 'real' conflict and the other one is the converted main document with the $Ref field pointing to itself.
As described in the technote http://www-1.ibm.com/support/docview.wss?rs=203&context=SW000&dc=DB510&dc=DB520&dc=D800&dc=D900&dc=DA900&dc=DA800&dc=DA440&dc=D600&dc=D700&dc=DB540&dc=DB400&dc=DA410&dc=DA450&dc=DA430&dc=DB550&dc=D100&dc=DA420&dc=DA460&dc=DB300&dc=DA470&dc=DA480&dc=DB100&dc=DA4A10&dc=DA4A20&dc=DA700&dc=DA4A30&q1=replication+conflict&uid=swg21087244&loc=en_US&cs=UTF-8&lang=all
this is possible when using the doc.save(True, ...) call in the Querysave event. Although, this issue was reported to be fixed in R5.0.12 but appears to still exist.
However, my code does not resave in the Querysave event but calls a LS agent after saving the open document to do further calculations and document updates. It then saves and closes the uidoc with SaveOptions set to 0 to avoid another save pop-up question.
Environment: Servers running R6.0.3 and 6.5.4, clients running in majority 6.5.x