Bug report

What Debezium connector do you use and what version?

IBMi connector 3.0.2

What is the connector configuration?

Kafka storage 
sanitize.field.names: true
database.hostname: ""
database.dbname: ""
database.schema:
database.user:
database.password:
database.server.name: topic
database.port: 8471
port: 8471
poll.interval.ms: 2000
transforms: unwrap
transforms.unwrap.delete.handling.mode: rewrite
transforms.unwrap.drop.tombstones: false
transforms.unwrap.type: io.debezium.transforms.ExtractNewRecordState
table.include.list: tablename
snapshot.mode: initial
log4j.logger.io.debezium: DEBUG
log4j.logger.org.apache.kafka: DEBUG
topic.prefix: topicname
database.history.kafka.bootstrap.servers: ${BOOTSTRAP_BROKERS_SASL_IAM}
database.history.kafka.topic: schema-changes
database.driver.secure: false
secure: false
database.secure: false
schema.history.internal.store.only.captured.tables.ddl: true
heartbeat.interval.ms: 1000# Sends heartbeat messages
include.schema.changes: true
slot.name: debezium# Logical decoding slot

What is the captured database version and mode of deployment?

7.4

What behavior do you expect?

When a snapshot finished successfully in the past, the connector should continue streaming after a restart.

What behavior do you see?

The connector logs 

No previous offset has been found
According to the connector configuration both schema and data will be snapshotted

Do you see the same behaviour using the latest released Debezium version?

Yes, but the issue does not occur in 3.0.1

Do you have the connector logs, ideally from start till finish?

Downgraded to 3.0.1 => no logs available

How to reproduce the issue using our tutorial deployment?

Use connector 3.0.2, run a snapshot and restart the connector. It does rerun the snapshot.

The problem is here:

In the As400OffsetContext there still is the private volatile boolean snapshotComplete = false; used by the isSnapshotComplete, but it should now use the snapshotComplete from the CommonOffsetContext