Repetition Protection and your InterWeave Flows
To avoid unnecessary processing of the same records in bi-directional sync we use a mechanism called Repetition Protection. All records, which are last updated in your CRM by the CRM User that is specified in the company profile, are skipped when querying your CRM for the records ready to be processed. This mechanism is included into scheduled flows and bulk load utility flows. It is not applicable if integration is unidirectional or the operations from your Financial Application to your CRM are set to None.