The documentation for MongoDB Connector fails with maximum BSON size error ] says:

This may be the case when Debezium (or rather the MongoDB change stream cursor) encounters a change event document with total size exceeding the BSON document size limit of 16 megabytes. Note that depending on the used capture.modethis issue can still manifest even when the actual value of the stored documents is significantly lower.
Starting with Debezium version 2.3.4 you can use the cursor.pipeline and cursor.pipeline.order properties to circumvent this error
First set the cursor.pipeline.order to user_first, then set cursor.pipeline to add the following aggregation stage.

...

But it doesn't mention anything about the oversize handling configuration properties introduced in 2.4?

cursor.oversize.handling.mode
cursor.oversize.skip.threshold