Connector getting Inactive due to replication slot PID already exists

Connector getting Inactive due to replication slot PID already exists io debezium debeziumexception_ creation of replication slot failed replication slot started lagging w88 slot online Caused by: DebeziumException: Failed to start replication stream at LSN; when setting up multiple connectors for the same database

w88 slot online : RuntimeException: SQLServerException: The connection is closed at io

timber stacks slot Debezium Connector is used to capture row-level changes and publish them as Events to your Kafka Cluster without the need to write custom TIP: If the query fails, it indicates that replication is not in place Go to the Setup tab of the connector, and click the Re-sync All Historical Data link