[whpalmer4]

I follow all of those best practices, religiously, and I still get the problem. If you've got repeating actions, those best practices are not sufficient.

I just constructed a test with a trivial OF database containing one repeating action (every 2 or 3 minutes), had both copies of OF running through the test, no sync communication errors, and it took only about 10 minutes for the two to get confused and have duplicate actions. I only manipulated the database on one side, the other one I just watched.

It really smells like the code to recognize an incoming action change from the sync is failing to match that change correctly against a change on the local copy when that change involves creation of a new instance of a repeating action. When it doesn't match, it keeps both. Logging why such comparisons failed during the sync might shed some light.

chidmf, if you look carefully, you may see that you can simply delete the completed actions which have seemingly come back to life. That's how my database is behaving, at least; your mileage may vary! Probably much easier to examine and repair the damage on the desktop.