---
sourceDocument: Yokohama Build or modify applications
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/application-development

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Reconcile changes

# Reconcile changes {#ariaid-title1}

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

Reconciling first compares the local instance to the parent, and then generates the
list of local changes and calculates the number of changes that are ready to pull from the
parent.

## About this task

A reconcile occurs automatically whenever you select a parent instance. You may need
to manually reconcile after an external disruptive event on the parent instance,
such as a clone or failover.  
Note:  
This process may take a while to complete depending on the size and age of the instance.

## Procedure

1. Navigate to AllTeam DevelopmentTeam Dashboard.
2. In the control panel, click Reconcile.
3. In the confirmation dialog box, click OK.  
   The list of local changes that have not been queued or ignored is recreated.
   If you had previously queued or ignored a local change, that designation is
   maintained.
4. **Optional:** On the completion page, click Show Results.  
   Review the instance comparison record.
   * The On Remote and not Local related list shows the versions that are ready to pull from the parent.
   * The On Local and not on Remote related list shows the local versions that are ready to queue or ignore.
   {#t_Reconcile__ul_fsr_fzc_bq}  
5. Click Team Dashboard.
6. [Pull versions](https://servicenow-prod.fluidtopics.net/diUKUhkwnpFn2Sn5fuSv4A "Pulling retrieves versions of customized records from the parent instance and adds them on the development instance. Pulling does not retrieve any versions for changes made by system upgrades, but it retrieves all versions for changes made by users, not just the current version.") from the parent instance and then [resolve any
   collisions](https://servicenow-prod.fluidtopics.net/rHCSjCvfuIgcZLrCC0FLlQ "A collision is detected when the pulled version and the current local version are modifications of a different version, indicating that someone else has modified the same record that you have modified. The team dashboard displays the number of collisions between the local and the parent instance.").
7. Review the local changes list and [queue or
   ignore changes](https://servicenow-prod.fluidtopics.net/L_BB0eW_e4NsLCLlU6o7~Q "Application developers can queue a local change for a push to ensure the changes are available to other developers."), as appropriate.

*[\>]: and then