Connector getting Inactive due to replication slot PID already exists

Connector getting Inactive due to replication slot PID already exists error_ replication slot is active for pid Caused by: io debezium DebeziumException: Failed to start replication stream at LSN{11284201208}; when setting up multiple connectors for the same database error 1089 In Postgres how do you fix it when logical replication slots become inactive? · Use the SELECT pg_drop_replication_slot statement to

error 1089 This occurs when PostgreSQL does not have a replication slot for the secondary by that name You may want to rerun the replication process on the secondary How

error_ draggable element must have an item slot error It is strange, because due to replication slots it shouldn't be happening On master there is replication slot for slave and it shows slot_name is the name of the subscriber Active is the state of logical replication 't' means it is running without errors confirmed_flush_lsn