Due to a server bug one of my calendars was no longer accessible, which resulted in the caldav resource stopping to replay any changes (because it retried the same change over and over). With the current approach of replaying revision by revision there is no good way around this; Either we abort and retry later, or we move on to the next revision which means that older revision will never be replayed.

Part of what is "unexpected" from a user POV is that *all* collections will stop replaying, not just the one affected collection, because contrary to pulling data from the server on replay we don't diff what's available on the server and locally, but we just replay the changes we have.

Nothing to address right now, but something to keep in mind.