If a command on the config server performs an early return without performing a write, it is expected that it will set the last seen operation time to the system's last operation time (setLastOpToSystemLastOpTime). This is to ensure that future reads will reflect the changes majority committed by previous operations.

During the process of committing a chunk split, the command checks whether a previous run of the command had already completed the operation (introduced by SERVER-72431).

If the split has been replicated to this node but is not yet part of the majority commit, the command will do an early return without waiting that time to be part of the majority.

Subsequent reads, such as a refresh, may not include that split, even though they were expected to be causally consistent as they were attaching a cluster time presumably inclusive of the split.