Here's a detailed explanation of the scenario:

1. Initial Triggering: I trigger an incremental snapshot on a connector using a Kafka signal.

1. Connector Deletion and Restoration: If the connector is subsequently deleted and then restored from its most recent Kafka Connect offsets (which includes the "incremental_snapshot_signal_offset"),

1. Reprocessing Signal: The signal that resides at the latest stored offset is reprocessed, thus causing the incremental snapshot to be re-triggered, regardless of whether the original snapshot had been fully completed.

Interestingly, this behavior does not manifest if there happens to be another signal for a different connector in the topic that was sent while the initial connector was active. This seems to prevent the reprocessing of the completed snapshot signal for the restored connector.