In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.

Bug report

For bug reports, provide this information, please:

What Debezium connector do you use and what version?

v3.3.1.Final

What is the connector configuration?

 
    config.action.reload = restart
    connector.class = io.debezium.connector.mongodb.MongoDbConnector
    errors.log.enable = false
    errors.log.include.messages = false
    errors.retry.delay.max.ms = 60000
    errors.retry.timeout = 0
    errors.tolerance = none
    header.converter = null
    key.converter = null
    name = connector123
    predicates = []
    tasks.max = 1
    transforms = [route]
    transforms.route.negate = false
    transforms.route.predicate = null
    transforms.route.regex = (.)mongodb(.)
    transforms.route.replacement = <XXXXXXXXXXXXXXXXXXXXXXXx>
    transforms.route.type = class org.apache.kafka.connect.transforms.RegexRouter
    value.converter = class org.apache.kafka.connect.json.JsonConverter

What is the captured database version and mode of deployment?

(E.g. on-premises, with a specific cloud provider, etc.)

MongoDb Atlas

What behavior do you expect?

Should have thrown error - 
The connector is trying to read change stream starting at " + sourceInfo + ", but this is no longer available on the server. Reconfigure the connector to use a snapshot mode when needed.

What behavior do you see?

Invalid resume token present, snapshot will be performed
Last recorded offset is no longer available on the server.

Task threw an uncaught and unrecoverable exception. Task is being killed and will not recover until manually restarted Exception:java.lang.NullPointerException: Cannot invoke "io.debezium.connector.mongodb.CollectionId.name()" because the return value of "io.debezium.connector.mongodb.SourceInfo.collectionId()" is null
at io.debezium.connector.mongodb.MongoDbSourceInfoStructMaker.struct(MongoDbSourceInfoStructMaker.java:39)
at io.debezium.connector.mongodb.MongoDbSourceInfoStructMaker.struct(MongoDbSourceInfoStructMaker.java:14)
at io.debezium.connector.AbstractSourceInfo.struct(AbstractSourceInfo.java:79)
at io.debezium.pipeline.CommonOffsetContext.getSourceInfo(CommonOffsetContext.java:58)
at io.debezium.connector.mongodb.MongoDbConnectorTask.validate(MongoDbConnectorTask.java:331)
at io.debezium.connector.mongodb.MongoDbConnectorTask.start(MongoDbConnectorTask.java:142)
at io.debezium.connector.common.BaseSourceTask.start(BaseSourceTask.java:261)

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

(Ideally, also verify with latest Alpha/Beta/CR version)

<Your answer>

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

(You might be asked later to provide DEBUG/TRACE level log)

Invalid resume token present, snapshot will be performed
Last recorded offset is no longer available on the server.

Task threw an uncaught and unrecoverable exception. Task is being killed and will not recover until manually restarted Exception:java.lang.NullPointerException: Cannot invoke "io.debezium.connector.mongodb.CollectionId.name()" because the return value of "io.debezium.connector.mongodb.SourceInfo.collectionId()" is null
at io.debezium.connector.mongodb.MongoDbSourceInfoStructMaker.struct(MongoDbSourceInfoStructMaker.java:39)
at io.debezium.connector.mongodb.MongoDbSourceInfoStructMaker.struct(MongoDbSourceInfoStructMaker.java:14)
at io.debezium.connector.AbstractSourceInfo.struct(AbstractSourceInfo.java:79)
at io.debezium.pipeline.CommonOffsetContext.getSourceInfo(CommonOffsetContext.java:58)
at io.debezium.connector.mongodb.MongoDbConnectorTask.validate(MongoDbConnectorTask.java:331)
at io.debezium.connector.mongodb.MongoDbConnectorTask.start(MongoDbConnectorTask.java:142)
at io.debezium.connector.common.BaseSourceTask.start(BaseSourceTask.java:261)

How to reproduce the issue using our tutorial deployment?

<Your answer>

Feature request or enhancement

For feature requests or enhancements, provide this information, please:

Which use case/requirement will be addressed by the proposed feature?

<Your answer>

Implementation ideas (optional)

<Your answer>