Failed to create Relationship - Access Connector for Dataverse

Question

If table migration fails partway through and you start again with the remaining tables, the migration wizard re-migrates related tables, even if they were already migrated, but with a "1" at the end. Then when the wizard attempts to create the relationship, it's trying to do so between the table being migrated and the <tablname>1 table instead, and fails. See attached. Then when migration is complete - it popups up the message telling us some tables were renamed because a table with the same name already exists on the endpoint.

Would be nice to have a mapping table popup so we could specify that the table is already there and to use that one (could be done similarly to how the (new) linked table manager works