No previous offset found — starting new snapshot

Root cause

The connector's Kafka Connect offsets topic was deleted, the connector was renamed, or offset data expired. Without an offset, Debezium treats the connector as new and starts from scratch, potentially re-delivering all historical data.

How to fix

1. Identify the exact connector/source partition and recover backed-up offsets where possible; read-only inspection must preserve the offset topic.
2. Plan a coordinated snapshot or reconciliation if recovery is impossible. no_data is not a general repair for lost offsets.
3. Schema-history recovery and source-offset recovery are separate tasks; recovery mode has connector-specific prerequisites.
4. Protect the compacted offset topic with replication, permissions, monitoring and a tested recovery procedure. A retention setting alone does not prevent loss.