Hi, following up on this request. We’re currently seeing this issue in a high-throughput use case where a single schema/data error causes the entire batch to be rejected. We then have to process the records individually to identify the bad record and send it to DLQ, which has a significant impact on throughput.