...
If, for any reasons, the syncing has failed and did not recover automatically, you will need to check the status and reset it. For that, use the Entity Sync Status feature in Webtools. If it's still in running state, put it back to not started status, in order for
the job to pick things again. Note that these jobs should run on the client(s) only and you should not run multi-instances of them. So you only have to care about this issue from the client(s) side.
Avoid TimeStamp issues
- Fix the timezone on all machines to be the same (sorry if this is an issue but I can't find another way)
- use an (preferably the same) NTP server to adjust the time on each machine. Remember that OOTB the minimun period of time used is 5 mins for push (1 hour for pull). So you should not get any issues as long as your machines have the "same time" between this window.
- If you get an issue with foreign keyd because the NTP server adjusted time inside a transaction, use the Check/Update Database feature in Webtools
...