Two change events with same clusterTime and same objectId but different fullDocument

We use the kafka-connect-mongodb connector to ingest all change events from a MongoDB cluster to Kafka.

We’ve noticed rare occurrences (~5 times over a year, lasting for 1-2 minutes) where we can get two events with the exact same $clusterTime and same $objectId but with different documents (for update events). When it happens, we can’t be sure of the exact update order.

Would you know if it is something that can happen when reading records from the change delta API? Is it possible that by design, we can have two different event documents with the same clusterTime and objectId?