Kafka source connector: heartbeat configuration not generating heartbeat messages

Hi all,

A few weeks ago I faced the “Invalid Resume Token” issue for the first time. It was caused because of an infrequently updated namespace, and because of that, I followed the prevention measures suggested by mongo’s documentation.

Now, my problem is that by adding the heartbeat configurations, the connector stopped sending the change stream events to the defined topic. Besides this, I also specified a topic to send the heartbeat messages as well, but this topic is not being created in kafka.

The following json is the configuration of my connector:

    "name": "staging-mongo-sk-licences-hb",
    "config": {
        "tasks.max": "1",
        "topics":  "staging-mongo.staging.licences",
        "collection":  "licences",
        "heartbeat.interval.ms": 60000,
        "heartbeat.topic.name": "staging-heartbeats",
        "connector.class": "com.mongodb.kafka.connect.MongoSourceConnector",
        "connection.uri": "${file:/etc/connectors-properties/auth.properties:mongo-uri}",
        "database": "staging",
        "topic.prefix": "staging-mongo",
        "change.stream.full.document": "updateLookup",
        "output.format.value": "schema",
        "errors.retry.timeout": -1,
        "poll.max.batch.size": 1000,
        "output.schema.value": "...."}

And this is the connector status running after being created with the above configurations.

    "name": "staging-mongo-sk-licences-hb",
    "connector": {
        "state": "RUNNING",
        "worker_id": ---
    "tasks": [
            "id": 0,
            "state": "RUNNING",
            "worker_id": ---
    "type": "source"

I don’t use SMTs, otherwise my connector would crash, so I don’t believe this is related to that.
Despite this, and even though the connector seems to be running, no change stream events nor heartbeat messages are being sent to the defined topics.

Is there anything I’m missing regarding this?

Thank you in advance,
Miguel Azevedo