Only that the group's committed position caught up with the topic's end. It does not establish that the external index durably applied, refreshed or made those records queryable. Kafka's consumer guidance discusses coordinating offset commits with external output. If the consumer commits before its output is safely recorded, a restart begins after those messages. The records may still be in Kafka retention, but the ordinary consumer path will not replay them. Confluent's consumer-lag documentation defines lag from stored and committed offsets, not from search visibility.

I would follow one missing document's source revision through the topic partition and offset, queue enqueue acknowledgment, worker attempt, durable index write and refresh or visibility point. A queue's successful enqueue may be the durable handoff if that queue is itself reliable and replayable. An in-memory task submission is not. If enqueue and offset commit are separate systems, there remains a crash window between them. One approach is to keep the processing position with the indexed output when the sink supports an atomic write. Otherwise design for at-least-once replay, idempotent updates keyed by document identity and source revision, and an explicit repair path for the gap. Do not claim Kafka's producer transactions make an arbitrary external search engine atomic with offset commits.

For monitoring, track the highest durably accepted source offset per partition and, separately, the highest query-visible revision. A single global maximum hides gaps across partitions. Alert on event age and reconciliation failures too, since a zero consumer lag graph can coexist with a broken downstream queue. The recovery decision depends on retention and whether the original source can be rescanned. If neither still has the missing changes, identify the data loss plainly and rebuild from the source of truth.

The hard question during an incident is which boundary made the record durable. A zero transport-lag graph cannot answer that. Until we can name the durable handoff and query-visible watermark, we cannot promise the document is searchable.