Using the Simulation Tolerance feature2017-10-27 12:21:54
The optional Simulation Tolerance settings, found on the General tab, only apply when Simulation is enabled. If any of these tolerance levels are set, the Simulation will determine the number of Adds, Mods and/or Deletes that will occur at sync time. If the Simulation determines the number of Adds, Mods or Deletes exceeds the tolerance level specified, the Simulation stage will end with an Error condition and the Sync stage will not take place during Batch Run.
There is no exact science to determining the right Tolerance levels for your situation. We suggest you review a handful of logs to determine an average number of each of the actions, and use your best judgment. Say you regularly see in the neighborhood of 100 deletes on Sync, but one of your logs shows 172 and that was perfectly normal as well. You may decide to set the Delete Tolerance to 175 to account for those occasional spikes in valid deletions, OR you may want to set the Tolerance to your average of 100, or just a little higher at 125, so that you are made aware of the occasions that aren’t your norm. You will likely find that you’ll need to adjust your Tolerance settings over time to get to a level where you are comfortable, and the Tolerance function is flagging unusual fluctuations in sync behavior.
Remember, too, that Simulation Tolerance only works if you run Simulation on every run of the connection. The Simulation phase must determine the Adds, Mods, and Deletes in order to prevent Sync from occurring in the case of a tolerance being exceeded.
If you have any additional questions about the Simulation Tolerance feature, contact Support for assistance.