Original User: MLF
Hello! I have just experienced this error. In my case, I know that if an invalid record is introduced to the parent database, the replica will fail. There are two ways to fix it: either rebuild the replica, in which case the invalid records will replicate, or fix the invalid records and the replica works again.
In this case today, I found and fixed the invalid records, but the replica still fails, and throws the same error referenced above. This is the first time invalid records have been introduced since we migrated our clients to 10.2, but our database is still on 10.
Only ~300 records were changed, so we are well below the 1000-record threshold referenced in the bug (2 features were invalid).
It will be unfortunate for our workflows (15 replicas synch every night/replica rebuild can only happen after hours, etc.) if this is a new issue starting in 10.2, but I'm not clear how the client version would matter.