Connector getting Inactive due to replication slot PID already exists

io debezium debeziumexception_ creation of replication slot failed   Dan hoki slot 96

DebeziumException: Failed to read next byte from position 1640249837 This happens if the binlog contains any special character

replication slot is already in use Here is the error from log: 2022 This occurs on line 141 here in the connector The name of the Postgres logical decoding slot created for streaming changes from a plugin and database instance Values must conform to Postgres replication

dot and slot blotters This includes changes to table schemas as well as changes to the data in tables MySQL uses the binlog for replication and recovery The Debezium MySQL  DebeziumException: Creation of replication slot failed DebeziumException: Creation of replication slot failed; when