@gcliff are sure you compiled the latest sync2 and atom feed modules?
yes i compiled both modules and got BUILD SUCCESS
@gcliff yesterday i told you to try interchanging them , make what was parent to child , and child to parent , and see.
can you also first share the server logs for child ??
no i cant see the logs related to Syncying. can you delete your logs text files under tomcat/logs and try syncying again .then paste the logs in the new log text file ??
i was meaning did you try solve one of the tickets that were raised about sync:roll_eyes:
hello devs I am working on this ticket, and I have been signing up patients on both the parent and child instances to see if I could land on this problem but I haven’t succeeded yet. Is there anyone of us who has got such a problem? Please any pointers? This has become my blocker. 
cc @mozzy , @jwnasambu , @gcliff, @sharif , @herbert24 , @lgilbert @tendomart , @odorajonathan, @dkayiwa, @ssmusoke
@irenyak1 that was the very first bug i noticed. what exactly are doing to reproduce it ?? this would be the simple steps
- Create a patient on the parent and sync it to the child.
- create a patient on the child and try to save it , it will first time throw that error
@irenyak1, I have encountered that on several occasions in that to solve it I have to first maybe add the relatives so as to bypass it. just keep creating patients from either instances am sure its gonna happen
1 Like
@mozzy can you please try to explain more because you left this hunging
@sharif its as simple as those two steps
2 Likes