Connector getting Inactive due to replication slot PID already exists

io debezium debeziumexception_ creation of replication slot failed   Dan wizard of oz ruby slippers slot machine

replication slot started lagging

Confirm that the connector has created a new replication slot and that it is in active state by querying the pg_replication_slots table Resume the write 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

v-slot linear rail replication slot is already in use Here is the error from log: 2022 This occurs on line 141 here in the connector state:FAILED, worker_id: :8083, trace: DebeziumException: Creation of replication slot failed at