Kafka Trigger Node Stops Listening After Some Time

Bug Description

The Kafka Trigger node in n8n stops listening to Kafka messages after a certain period of time. Once the node stops listening, it does not resume or reconnect to Kafka unless the workflow is manually restarted. This issue makes it unreliable for long-running workflows that rely on continuous message consumption from Kafka.
issue
If this has happened to anyone else, please help me.

As you were able to provide, the n8n team responded to the error report on github and said they are investigating. There may be nothing else to do but wait or try an older version of n8n.