We have a similar issue now. The possible guess that during rebalancing process this service wasn't added to the consumer group and no new events are assigned to it, so it's just a service in memory without processing.

We didn't find the solution