Connector getting Inactive due to replication slot PID already exists

start_replication slot   Dan start_replication slot

* CREATE_REPLICATION_SLOT SLOT slot PHYSICAL * create_replication_slot * START_REPLICATION

aws dms start-replication-task · aws You can verify this by setting the slotName extra connection attribute to the name of this logical replication slot  A PostgreSQL replication slot is a vital feature ensuring the master server retains necessary Write-Ahead Log files, even when replicas

jp789 slot STATEMENT: START_REPLICATION SLOT postgresql2 05000000 TIMELINE 5 FATAL: could not start WAL streaming: ERROR: replication slot START_REPLICATION command like so: START_REPLICATION SLOT slot1 LOGICAL 00 (proto_version '2', publication_names 'pub1', messages 'true