Applies to Riva On-Premise 2.4.42 or higher.
The behaviour described in this paragraph is the same as in previous releases. Before a sync, various Riva settings are used to determine where to store the transactions metadata, in one or more subfolders of the Riva\Transactions folder. If any of those settings was changed since the last sync, the calculated subfolders could be wrong. If the metadata from the previous sync is not found where it was expected to be, it would be better not to sync, because attempting to sync in those conditions might have unintended results.
Riva 2.4.44 or Higher
By default, the system is configured to prevent the sync from executing when any transactions metadata is not found where expected. When transactions metadata is not found in the expected subfolders of the Riva\Transactions folder, an error is issued and the sync stops.
In Riva 2.4.44 or higher, after some preparatory steps, it is possible to make legitimate changes to the location of any transactions metadata.
Riva 2.4.42 and Riva 2.4.43
The system is not configured by default to prevent the sync when the transactions data is missing, but it is possible — and recommended — to configure Riva to prevent the sync from executing when any transactions metadata is not found where expected. If you follow our recommendation, when transactions metadata is not found in the expected subfolders of the Riva\Transactions folder, the error "Mismatched policy transactions folder" is issued and the sync stops.
In Riva 2.4.42 or 2.4.43, if you want to prevent the sync when a metadata folder is not found, follow this procedure.
To detect when transactions metadata has been misplaced and prevent the sync in that case:
If the Mismatched policy transactions folder error has occurred and you have used a link to see this article, be aware that in most cases, the error indicates a misconfiguration that can result in duplicate records or other unexpected results. To solve the issue, contact the Riva Success Team.
The location of some transactions metadata legitimately needs to change when, for example, a user is moved from one sync policy to another. If the sync has been prevented from occurring when some transactions metadata cannot be found and you need to change the location of any transactions data, action is required on your part; otherwise, the sync stops when the user is moved from one sync policy to another.
To temporarily prevent the sync from stopping if you want to change the location of any transactions data:
Article ID: 1557
Last updated: 05 Nov, 2020