(In reply to comment #2) > You're correct. I think you're asking me to verify this. So: > > ScheduleWorld is configured to be 'client wins'. I don't think that this is a useful policy for delete/update conflicts because data can get lost. I have added it as a caveat to the new test/README.scheduleworld document: ScheduleWorld resolves conflicts where the client deleted an item that was updated on the server by deleting the item on the server (Bugzilla #4369). Advice: copy items instead of updating them if they were deleted elsewhere, otherwise the updated item may get lost later on. If you think changing the policy would be useful, then let's reopen this issue.