Currently, when using deeplinks to call to connectWithURI with reuseExisting=true, if a connection string is not saved due to an identical connection string already existing, the user is connected with the old connection string. As this old string may have a different name, the user may be confused as to why their new connection hasn't been saved. Provide some messaging or window pop-up explaining this behaviour is expected and for the user to remove the old connection string if they wish to create a new one (or set reuseExisting to false if the use is directly calling the deeplink).