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

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# General guidelines for excluding a table from cloning

# General guidelines for excluding a table from cloning {#ariaid-title1}

* Release version: Yokohama
* 
* Updated September 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

A reference topic that includes general guidelines to exclude a table from cloning.

Workflow context data
:   Excluded workflow context data includes records stored in the `wf_context` table, and in related tables with names starting with a prefix of `wf_`. If workflow contexts were included, this process
    helps to prevent the occurrence of workflow timer syncing issues. Issues can occur due to the length of the cloning process.

Excluding child tables of the task table
:   When excluding child tables of the task table, which use the [table per hierarchy extension model](https://www.servicenow.com/docs/LEjy0~kDYQlt9HXyuGseAg "Table flattening stores a hierarchy of related tables as one table in a relational database."), child tables are excluded. You don't need to exclude the parent Task table together with the child table.

Using wildcards
:   You can use wildcards to exclude several tables from cloning with one entry. For example, <kbd class="ph userinput">sys_script.*</kbd> excludes all tables starting with <kbd class="ph userinput">sys_script</kbd>.  
    Note:  
    The wildcard has to include the dot '.' before the asterisk.

Excluding or preserving related tables
:   To preserve or exclude related tables, you must preserve and exclude the following tables. If any of the tables are missed, the customer may not be able to log in to the instance after a clone.

    * sys_user
    * sys_user_role
    * sys_user_group
    * sys_user_grmember
    * sys_group_has_role
    * sys_user_role_contains
    * customer_contact (if the Customer Service Management plugin is active)
    {#clone-exclusions-guidelines__ul_abq_zkz_5gc}

Tables that can't be excluded
:   `sys_db_object` and `sys_db_object.*` can't be added to the exclusions.