---
sourceDocument: Australia ServiceNow AI Platform Administration
sourceDocumentLink: https://www.servicenow.com/docs/r/platform-administration

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# General guidelines for optimizing your clone duration

# General guidelines for optimizing your clone duration {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

A reference topic that includes general guidelines to optimize your clone duration when requesting a clone.
Configuring additional settings for your clone request can significantly increase your clone completion time.
When creating a clone request, consider the following guidelines.

* Set the amount of data copied from the task table to <kbd class="ph userinput">Full</kbd>. This option clones all data from the task table and its child tables to the target instance.  
  Note:  
  The <kbd class="ph userinput">Last 90 days</kbd> option can increase duration, as it takes longer to remove records from the task table that are older than 90 days after restoration.
* Selecting Exclude Attachment Data on the clone request form can add to your clone duration.
* Don't preserve large amounts of data in your request. If you must preserve table data, such as users, groups, and roles, consider exporting the records to a file and importing them after cloning.
* Add conditions to the preservers configured for the clone request to only preserve the data that you need.
* Use clone chaining to split up your request, see [Clone terminology](https://www.servicenow.com/docs/WmY0lMPR7eIQEpZSw07gYg "A reference topic that contains various terms and definitions for cloning.").
{#clone-duration-optimization__ul_xlm_qkf_cgc}