You ran the Task document and everything worked perfectly. The next day, many replication conflicts appeared. What went wrong?
Possible Explanation:
1. Think of the Sentinel as any other user when you run Tasks. If your users will be updating documents on replica copies of the database at the same time the Sentinel is, replication conflicts will occur.
Possible Solutions
1. If you want to minimize replication conflicts, schedule to Sentinel to run after most or all users do daily and nightly replication.
2. Do not needlessly update documents. Think about the update and try to combine two updates, so you are only impacted once.
3. Schedule Updates in two parts:
a. Do Add Unique anytime at all. These are new records which do not exist anywhere else in this Notes replica.
b. Do Update on weekends or other times after all users have replicated their changes to the database on which you are working.
The easiest way to do this is to copy and paste your Schedule document and change the scheduled times of each document, along with the Add Unique andUpdate settings.
Tips on Scheduling the Sentinel When designing an application that may be replicated across many servers and laptops, try to put as many fields from one or more external sources on one form. Additionally, make those field Computed so that users cannot update any part of the form. This enables you to schedule these updates at any time, because the Sentinel will be the only "User" updating those records. This will avoid all replication conflicts.