Change data capture reads committed database changes and applies them elsewhere. The first copy usually combines a table snapshot with a change log. Those two views need an agreed position, or an update during the snapshot can disappear between them. Record the source position associated with the snapshot and continue from that boundary using the source's supported protocol.
Delivery order also matters. A retried update must not overwrite a newer value, and a delete needs a representation that survives replay. Keep a source sequence or log position with each applied record. A consumer can then ignore an older version even when it arrives later. Retention is a recovery limit: once the required log segment expires, resetting an offset cannot recreate it. You need a new consistent snapshot or another retained source.