An agent is processing large record set of notes documents and the agent saves each and every document . Then the last modified date and time is changed for every document.
The issue we are facing is the agent modifies the documents with future time. Sample Example is below for the reference.
the agent start time is 09/25/2014 2:50:10PM and the end time is 09/25/2014 2:53:10PM. From log, it is clear that it took 3 mins for the agent to process all documents. There are thousands of documents modified with future time like 2:54, 2:55 etc.
It doesn’t happen to all documents, say for example if there are 12000 documents, it process the first 6k or 7k correctly and then it starts to give the future time for the rest of the documents.
If the record set is huge like 100,000, then the records at the end will have atleast 30 to 40 mins future time.
Subject: Agent stamping future time for last modified date and time
I can’t find any references on this, but I recall reading about it a few years ago. If I remember correctly, the problem occurs if your agent is processing and saving more than 100 documents per second. This causes the timestamp to drift forward. The workaround is to deliberately slow down the agent.
(I’m pretty sure that this has been fixed in more recent versions, which may explain why I can’t find any references to it.)
