[Ken Case]

Originally Posted by whpalmer4

I've seen a couple of cases where it said it couldn't sync because I had reverted the local database (and I knew that no such thing had happened). I hit the cancel button, synced again and everything was happy (and my data intact). It seems like that should be safe, but perhaps someone with definitive knowledge about the sync code could comment...

Yes, it's safe to cancel and sync again. If it's a real issue, it will report the error when you re-sync.

We've finally managed to reproduce this in a development build, though we haven't yet figured out how to reproduce it reliably. But it's a start; hopefully we'll be able to track this down and fix it soon.