In the event that a ServiceNow instance has been renamed and there are already existing clone target records created for that instance from another source instance, the clone request may fail as the clone target record contains a URL and other connection information that ho longer references a valid ServiceNow instance.
The error message received when attempting to submit the clone will usually indicate "Unknown host" and the clone request will not be submitted.
Attempting to create a new clone target for the renamed instance will fail, because the target instance still retains the same sys_id regardless of the instance name.
Furthermore, attempting to delete the previous clone target record from the source will usually generate a message such as the following and prohibit the deletion:
The current record cannot be deleted until all XX instance clone records referencing it are deleted.
This is because this record references some number of previously completed or requested clone requests (corresponding to the XX number of records) on the source instance. Attempting to delete these related clone request records will also usually be unsuccessful.
In order to allow a clone from the renamed instance to be submitted without errors in this case is to rename various fields of the clone target record.
To perform this rename, follow these steps:
Updating the Name or URL field of the clone target request will automatically cause the other necessary fields of the record to be updated as well (i.e. database_url, database_user, etc).