---
sourceDocument: Zurich ServiceNow AI Platform Capabilities
sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/servicenow-platform

 Release :

    - zurich

ft:locale :

    - en-US

ft:publication_title :

    - Zurich ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# Cancel scheduled replication

# Cancel scheduled replication {#ariaid-title1}

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

Cancel scheduled replication by deactivating or deleting a producer replication set.

## Before you begin

Role required: admin

## About this task

Once set, you can't disable scheduled replication on a producer replication set; the option becomes read-only. You can either deactivate the set or delete and recreate it.

## Procedure

1. Navigate to Instance Data ReplicationProducer Replication Sets.
2. Select the producer replication set for which you want to stop scheduled replication.
3. Stop scheduled replication before another run occurs.
   * Pause scheduled replication indefinitely by selecting Deactivate. This option stops replication before the next schedule run.
   * Stop scheduled replication by selecting Delete. This option deletes the producer replication set. If you plan to recreate the producer replication set, record the settings you configured before you delete the replication set.
   {#cancel-seeding__choices_fhd_p3c_hdc}

## Result

Scheduled replication ends. After deactivating the producer replication set, any in progress seeding requests will complete, but pending requests will not be processed.

## What to do next

If you intend to resume scheduled replication, you can sync records that weren't replicated during the deactivation period by running a data comparison request. See [Comparing replicated data between instances in Instance Data Replication](https://www.servicenow.com/docs/ZwBxZE8EjVPFz7VN4nDp_g "Find missing or mismatched records by comparing replication data between instances in Instance Data Replication (IDR)."). Alternatively, you can replicate missing records by performing a partial seeding request from the Inbound Entries related list on the consumer replication set.

*[\>]: and then