---
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


---

# Pull exceptions

# Pull exceptions {#ariaid-title1}

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

Pulling ignores versions when certain conditions occur.
{#r_PullExceptions__table_whc_vvb_bq__entry__2}

| Issue | Description |
|-|-|
| Matched an exclusion policy | An exclusion policy prevents pulling changes for records matching the policy conditions. The pull identifies the changes but does not include versions for these records. |
| Private properties | A private property is excluded from all Update Sets and pulls. |
| Collisions | A collision is detected when the pulled version and the current local version both include modifications to the same record. You must resolve all collisions before you can pull. |
| Previously resolved collisions | When you resolved a collision by accepting either the pulled version or local version of a record, the pull remembers your decision and accepts the version that you indicated as a "previously resolved collision". |
| Skipped | Pulls skip versions where there is a problem with the version record such as a corrupt or missing version. |
[Table 1. Pull exceptions table]

{#r_PullExceptions__table_whc_vvb_bq}