Skip to Main Content
HCL Domino Ideas Portal

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Status Under Consideration
Workspace Domino
Categories Administration
Created by Guest
Created on Feb 8, 2023

Future date/time stamps are noticed in notes agents, indexing, and also design elements.

Future date/time stamps are noticed in notes agents, indexing, and also design elements.

Below technotes\kb articles are applicable.

Why a Notes Database may show future dates:

The last modified date of the document when the agent is executed becomes to be the future date:

- Those articles state that this is a software limitation as detailed below.

By mass-updating of documents, the modified date can be moved into the near future because every document needs a unique millisecond timestamp, and therefore future dates/times are needed. This is not a Bug and is Software Limitation.

The limitation is not yet fixed. You can follow the below KB articles, if this issue is fixed the KB article will be updated with the correct version details.

SPR#HKAI63QAKG states this is considered an enhancement request but no corresponding AHA request is found on the IDEA portal.

  • Attach files
  • Guest
    May 30, 2024

    Hello, just to note that this Domino behavior is quite annoying and can be a quite strong obstacle to hold a large number of documents in Domino databases.

    This case of massive document update via agents is not a single one that may trigger this issue. The same can also happen during a massive replication. Even a normal maintenance operation where replication history is being cleared on a database replica containing a large number of documents or that database is being compressed can cause it.