What Debezium connector do you use and what version?

What is the connector configuration?
What is the captured database version and mode of depoyment?

Refer test setup of DBZ-6399 comment (https://issues.redhat.com/browse/DBZ-6399?focusedId=22252751&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-22252751)   

What behaviour do you expect?

Offsets of consumer group id "connect-sink" are committed.

What behaviour do you see?

In logging:

2023-05-12 07:51:09,153 WARN   ||  WorkerSinkTask{id=sink-0} Ignoring invalid task provided offset testtable-0/OffsetAndMetadata{offset=8, leaderEpoch=null, metadata=''} -- partition not assigned, assignment=[sandbox.debezium_source.testtable-0]   [org.apache.kafka.connect.runtime.WorkerSinkTask]
 

Notice: Problem is somehow related to this SMT 
"org.apache.kafka.connect.transforms.RegexRouter"
because if no topic name transformation is configured, the offsets are committed as expected.

Idea: It would be great if this RegexRouter SMT could be replaced by an "Regex-like" enhancement of the  "table.name.format" configuration setting in DefaultTableNamingStrategy.java

Do you see the same behaviour using the latest relesead Debezium version?

not tested

Do you have the connector logs, ideally from start till finish?

Refer logs in test setup of DBZ-6399 

How to reproduce the issue using our tutorial deployment?

Refer test setup of DBZ-6399