Last week our server had an error and we needed to restart it and after 20 minutes running we found that the date was 15 days ahead .
We quickly changed the date and now we are experiencing issues with some users .
Databases are now like they were created on october 10 on the server .
Some users have local replicas on their computer and all the changes that they do ( move to folder, read mails ) are not replicating to their replica on the domino.
I would suggest opening a PMR. There are some areas where Replication uses a timestamp other than the DataModified or NonDataModified timestamps for a database. It’s possible that this might cause the replication history to get out of sync with the document modified times. It might require custom debug built for your server to track down the root cause, and a PMR is the appropriate way to request something like that.
The only thing I can suggest is creating views in the dbs by @modified date and cut and paste all the docs that got created in the future. You might be able to get by by with just a resave of the doc but not sure what happens when replication sees a doc that was created after it was last modified.
Clearing history should be done as well. If you have dbs that where created in the future and not used yet you might as well delete and recreate them just incase,