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?

mongodb connector 2.5

What is the connector configuration?

'{"name":"monogdb-connector","config":{"connector.class":"io.debezium.connector.mongodb.MongoDbConnector","mongodb.connection.string":"mongodb://localhost:27017","topic.prefix":"mongodb","database.include.list":"mydb","collection.include.list":"mydb.idtest","exactly.once.support":"required","name":"monogdb-connector","heartbeat.interval.ms":1000}}'

What is the captured database version and mode of depoyment?

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

on-premises , MongoDB 5.0 in 3 member replica set

What behaviour do you expect?

when a new record is inserted into the mongo collection they should reflect into corresponding topic .

What behaviour do you see?

The connector stopped sending messages into the topic even though there are changes occuring in table .After six hours or above one day i am seeing this before that all are ok .
There is no error or any specific log corresponding to this. The heart beat log is as usual but the connect-offset messages are stopped but there are changes happening for the mentioned  table.

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

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

yes

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

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

No Error nothing 

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)