Chronos - Update documents?

I had my boss come ask what was going on with the server (never a good thing) because he was seeing several thousand replication events between his mail and a few other databases. After examining the server logs and the documents what I found was the following.

All documents were modified by the server about the same time that Chronos was running. Subsequently agents that are triggered by changed/modified documents ran and sent thousands of emails to external and internal.

Chronos started @ 04:29:29 PM

The first modified document in one database 04:29:37 PM

Chronos ended @ 04:32:41 PM

The last modified document in the same database 04:34:17 PM

Log shows no other events (besides mail routing) and domain indexer. The domain indexer is throwing off an error in the bosses mail file - “Database is currently being indexed by another process”

I searched for update or fixup in the log thinking something may have detected some corruption and fired off either task, but nothing was found.

Looking for any ideas, suggestions, etc.

Thanks!

Brent

Subject: AdminP and user rename

The user did not follow my advice and carry her newly modified ID to any other machine she used, so two days ago she signed on to a machine with her old ID and that created a new set of AdminP requests. The reader/author update runs Friday @ 3:00 and that was what caused the server to mark documents. The problem is that the documents that we marked did not have any values in Name/Reader/Author fields. The only place the users name showed was in the $UpdatedBy, but it had not been modified.

I know what caused the update, but I am unclear as to why the server updated the documents it did. Since this was the second run of the AdminP rename processes (last was done on 5/7) I do not know why there was anything left to update. Taken with the fact that it seemed to update many documents that did not need to be updated, I am stumped.

Any help again would be appreciated.

Thanks!

Brent