We have the same issue after migration to MSK Connect 3.7.x. According to conversation with AWS support it is related to some issue on their side (MSK Connect) and it should be fixed soon - on 31 Jan 2025