No, this particular message we failed to process due to limitations (visible in error logs), but we managed to recover connector and push it to work further. What we did was: Python script took CDC signature, processed messages one-by-one and thus located the faulty message, then skipped it, got the next CDC signature. (For us problem was due to we were sending full documents to Kafka, so switching to sending only change part, reduced message size thus allowing to skip it), after we received next CDC signature we wrote it into Kafka Offset topic, so the connector continued to work.
But then we decided not to use connector that receives full documents at all, so problem was not actual anymore.
But I believe if you are seeking for long term working solution - we do not have it, unfortunately.