September 23, 20214 yr I'm checking a sync of a user and mirrorsync is updating all his records. It's like Mirrorsync completely forgot what was synced or not and is forced to check every record, It's extremely long. Any known cause for this ? Edited September 23, 20214 yr by sfpx
September 24, 20214 yr This is almost certainly happening because those records were updated on the server. Check the modification timestamps on the hub, and you’ll probably find that all the records were recently modified. This could be caused by replacing field contents, or a looping script.
September 24, 20214 yr Author I pretty much can assure you those records were not updated on the server prior to the sync. The sync was actually updating both the server and the device records. So after the sync, all his records were updated on the server (with timestamps in the sync period) I will send you the logs Edited September 24, 20214 yr by sfpx
October 12, 20214 yr Author Looking at the log I can see that the problem occurs when the recovery mode is activated. This keeps happening for many users causing ultra long syncs. This happened this morning again. What is the recovery mode ? What cause its activation ? How can we avoid it ? Edited October 12, 20214 yr by sfpx
Create an account or sign in to comment