"There is already a clone scheduled for the target instance" while raising adhoc clone request when there may be recurring clonesIssue We might observe an issue where the user is not able to schedule a clone. While scheduling getting a message saying " There is already a clone scheduled for the target instance" and the clone request is put on hold. This is in the case where there are already recurring clones scheduled across the same source and target with pre-determined frequency intervals. A query can be raised saying since there are already multiple clones scheduled, why an Adhoc clone cannot be raised as well.ResolutionAs per current system behavior, the clone engine will allow the creation of recurring clone requests from the NY version onwards. In that case, multiple requests will be in place for the same clone source and target combination and will not be restricted by the above validation(provided there are no pending clones to the same target). In this case all the clone requests are placed in the instance at one shot. But in case there are pending clones, already existing for the same target, raising a new clone request will still point to the above validation and will give the error message.** The workaround to go for an ad-hoc clone request to the same target as of now:Cancel all the requested recurring clones from the UI.Schedule a clone request as per your convenience from source to target instance.Once the above clone is completed, create a recurring clone schedule again.