Clone target error: clone operation failed on target instance

Target instance is in a non-cloneable state such as being in maintenance mode, having active sessions, or being in the middle of an upgrade process. (high likelihood)

Insufficient storage space on the target instance to accommodate the clone data from the source instance. (high likelihood)

Active user sessions or scheduled jobs running on the target instance during the clone window, preventing the clone operation from proceeding. (medium likelihood)

Network connectivity issues or timeouts between the source and target instances during data transfer. (medium likelihood)

Target instance configuration issues such as incorrect clone settings, blocked clone operations, or missing required system properties. (low likelihood)

Step 1: Check the Clone Monitor at System Clone > Clone Monitor to view detailed clone status and error messages for the specific clone operation.

Step 2: Verify the target instance state by checking System Diagnostics > Stats and ensuring the instance is not in maintenance mode or upgrade process.

Step 3: Review storage capacity on the target instance through System Diagnostics > Stats > Database to ensure sufficient space is available for the clone data.

Step 4: Check for active user sessions on the target instance at System Security > Active Sessions and terminate non-essential sessions if found.

Step 5: Review scheduled jobs on the target instance at System Definition > Scheduled Jobs and disable or reschedule any jobs that might interfere with cloning.

Step 6: Examine system logs at System Logs > System Log for detailed error messages and network connectivity issues during the clone operation timeframe.

Step 7: Verify clone configuration settings and ensure the system property glide.clone.enabled is set to true on the target instance.

Step 8: Retry the clone operation during a maintenance window when the target instance has minimal activity and all prerequisites are met.