Umbraco Cloud
CMSHeartcoreDXPMarketplace
  • What is Umbraco Cloud?
  • Frequently asked questions
  • Security
    • Web Application Firewall
  • Sustainability Best Practices
  • Getting Started
    • Explore Umbraco Cloud
    • The Cloud Portal
      • Organizations
      • Sustainability Dashboard
    • Project Overview
    • Environments
    • Flexible Environments (beta)
    • Baselines
      • Baseline Merge Conflicts
      • Break Reference between Baseline and Child Project
      • Handling configuration files
      • Pushing Upgrades to a Child Project
    • Plans
    • Migrate to Umbraco Cloud
    • Repositories in a Cloud Project
    • Best Practice for Working in Teams
    • Migrate between regions
  • Set up
    • Ready to Set Up Your Project?
    • Working with a Local Clone
      • Legacy Umbraco Visual Studio Setup
    • Manage Environments
    • Project Settings
      • Managing Transport Security
      • CDN Caching and Optimizations
      • Dedicated Resources
      • Upgrade your Plan
      • Public Access
      • Managing Hostnames
        • New Certificate Authority for custom hostnames
        • Rewrite rules
        • Custom Certificates
      • Management API Security
      • Umbraco CI/CD Flow
        • Cloud API For CI/CD Flow
        • Configuring a CI/CD pipeline
          • Azure DevOps
          • GitHub Actions
        • Troubleshooting
        • Known Limitations and Considerations
      • External Services
      • Usage
        • Bandwidth
      • Availability and Performance
      • Team Members
        • Technical Contact
      • Secrets Management
      • Project History
    • Private NuGet Feed on Umbraco Cloud
    • Going Live
    • Media
    • External Login Providers
    • Azure Blob Storage
      • Connect to Azure Storage Explorer to upload files manually
      • Connect and Upload Files Programmatically to Azure Blob Storage
    • Users
    • Multi-Factor Authentication
    • Application Insights
    • Config Transforms
    • SMTP Settings
    • Payments
      • Subscription migration information and FAQ
    • Power Tools (Kudu)
      • View the Files on your Cloud Environments
      • Generate UDA files
      • Manually run Extractions on your Cloud Environments
  • Deployments
    • Deployment
    • Deploying between environments
    • Transferring Content, Media, Members, and Forms
    • Deploying Deletions
    • Deployment Webhook
    • Deploying Changes
    • Umbraco Forms on Cloud
    • Deploy Dashboard
    • Hotfixes
      • Apply hotfix by manually moving files
      • Apply hotfix by using Git
    • Restoring Content
      • Partial Restores
  • Databases
    • Keep Your Data Secure and Accessible
    • Working with databases
    • Database backups
    • Database
      • Connecting to the Database on Mac
    • Working with a Cloud database locally
  • Product Upgrades
    • Stay Up to Date with Umbraco Cloud
    • Product Upgrades
    • Major Upgrades
    • Minor Upgrades
    • Version Specific Upgrades
      • Migrate from Umbraco 8 to the latest version
      • Migrate from Umbraco 7 to Umbraco 8 on Umbraco Cloud
    • Upgrade your projects manually
      • Manual upgrade of Umbraco CMS
      • Manual upgrade of Umbraco Deploy
    • Dependencies on Umbraco Cloud
  • Troubleshooting
    • Resolve Issues Quickly and Efficiently
    • Troubleshooting FAQ
    • Log files
    • The Umbraco Backoffice
    • The Frontend
    • The Umbraco Cloud Portal
    • Site Performance checklist
    • Troubleshooting deployments
      • Extraction error: Config transforms failing
      • Extraction error: Data Type collisions
      • Dependency Exception
      • Merge Conflicts on Flexible Environments
      • Troubleshooting deployments failing with no error message
      • Troubleshooting duplicate dictionary items
      • Troubleshooting language mismatches
      • Path too long Exception
      • Schema Mismatches
      • How to resolve collision errors
      • Extraction error: "Type not found! "
    • Cloud Errors
  • Release Notes
    • Overview 2025
      • April 2025
      • March 2025
      • February 2025
      • January 2025
    • Overview 2024
      • December 2024
      • November 2024
      • October 2024
      • September 2024
      • August 2024
      • July 2024
      • May 2024
      • April 2024
      • March 2024
      • February 2024
      • January 2024
    • Overview 2023
      • December 2023
      • October 2023
      • September 2023
      • August 2023
      • June 2023
      • May 2023
      • April 2023
      • March 2023
      • February 2023
      • January 2023
    • Overview 2022
      • December 2022
      • November 2022
      • September 2022
      • August 2022
      • June 2022
      • May 2022
      • April 2022
      • March 2022
      • February 2022
      • January 2022
Powered by GitBook
On this page
  • Table of content
  • Video tutorial
  • Using the error message
  • Deciding which file you want to use
  • Removing the unused file
  • Getting your environments in sync
  • Does your Development Environment still have the red indicator?

Was this helpful?

Edit on GitHub
Export as PDF
  1. Troubleshooting
  2. Troubleshooting deployments

How to resolve collision errors

PreviousSchema MismatchesNextExtraction error: "Type not found! "

Last updated 1 month ago

Was this helpful?

This guide is for solving collision errors on your Umbraco Cloud project. Use this guide when you encounter an error like this:

Some artifacts collide on unique identifiers.
This means that they have different Udis, yet
they refer to the same unique Umbraco object
and therefore cannot be processed.
---------------------------------------------
Collisions for entity type "document-type":
Collisions for unique identifier "home":
    UdaFile: ~/deploy/revision/document-type__4c04d968448747d791b5eae254afc7ec.uda
    UdaFile: ~/deploy/revision/document-type__f848c577f02b4ee5aea84f87458072a4.uda

The error means that two (or more) .uda files have been created for the same entity. The .uda files contain schema data for each of your entities. For example, Document Types, Templates, Macros, Dictionary Items, Data types, and so on. For a full list of these entities, see .

In this example, there are two .uda files that share the same alias which leads to a conflict: it is impossible for Deploy to know which of the files to use, so it gives up and sends an error back.

If the collision error involves Dictionary Items, use this guide instead:

You can run into an error like this on all of your Cloud environments. Sometimes you might also run into it on a local clone of your project.

This guide uses an example where two files are colliding across two environments: a left-most environment and the Live environment.

For clarity, the left-most environment will be referred to as the Development environment throughout the guide.

Table of content

When you have two or more Cloud environments, it is recommended that you only work with schema on local, Development, or flexible environments.

Video tutorial

Using the error message

In the example above, the entity involved is a Document Type with home as the alias. There are two colliding files both located in the /deploy/revision folder. The files are colliding because they share the same alias but have different GUIDs (also the name of the files).

Deciding which file you want to use

In order to fix this problem, you will have to decide which of the colliding entities is the correct one and the one you want to use on your Live environment.

Let's use the example from the beginning of this article, where two .uda files for the Document Type "home" are colliding.

Some artifacts collide on unique identifiers.
This means that they have different Udis, yet
they refer to the same unique Umbraco object
and therefore cannot be processed.
---------------------------------------------
Collisions for entity type "document-type":
Collisions for unique identifier "home":
    UdaFile: ~/deploy/revision/document-type__4c04d968448747d791b5eae254afc7ec.uda
    UdaFile: ~/deploy/revision/document-type__f848c577f02b4ee5aea84f87458072a4.uda

For this example, it’s decided that the Document Type currently used on the Live environment is the one we want to use going forward.

In order to figure out which of the two colliding .uda files are the one for the Document Type being used on the Live environment follow these steps:

  1. Run one of the following queries on the database, depending on the type you see the error with

    • Run the following query, if the error states that the error is a Collisions for entity type "document-type":

    SELECT uniqueId
    FROM umbracoNode
    WHERE id = (SELECT nodeId FROM cmsContentType WHERE alias = '[The alias from the error message eg. home]')
    • Run the following query, if the error states that the error is a Collisions for entity type "template":

    SELECT uniqueId
    FROM umbracoNode
    WHERE id = (SELECT nodeId FROM cmsTemplate WHERE alias = '[The alias from the error message eg. home]')
    • Run the following query, if the error states that the error is a Collisions for entity type "macro":

    SELECT uniqueId
    FROM cmsMacro
    WHERE macroAlias = '[The alias from the error message eg. home]'
    • Run the following query, if the error states that the error is a Collisions for entity type "data-type":

    SELECT uniqueId
    FROM umbracoNode
    WHERE text = '[The alias from the error message eg. home]'
  2. The above-mentioned queries will give you the udi of the entity in use on the live environment.

You now know which .uda file you want.

Removing the unused file

We strongly recommend that you resolve this locally since this will ensure that the changes you make are added to your Git repositories. Otherwise, you may end up having the same problem next time you deploy.

  1. Clone down the Development environment to your local machine.

  2. Run the project locally and verify that you get the same extraction error as on your Cloud environments (HINT: look for a deploy-failed marker in your local /deploy folder).

    • When you run the project, you should see an error message in the browser once the site starts to build.

  3. Remove the wrong .uda file (It's the one we did not find in the live environment just before) from the /deploy/revision folder - you will not be able to see the Document Type in the backoffice because of the failed extraction.

  4. Open the Umbraco Backoffice and go to Settings -> Deploy to see the Deploy dashboard.

  5. Select Schema deployment from data files in the dropdown.

  6. You will now see a deploy-complete marker in your local /deploy folder.

Does the error mention Templates? You might experience that .uda files for a template are colliding. When this is the case, we recommend that you copy the content of the cshtml file associated with the template you want to keep on your project - this way you'll have a backup of the code you want to use.

Getting your environments in sync

Before pushing the changes to the Development environment, you need to access the backoffice of the Development environment and remove the Document Type from there.

Commit and push the changes from your local clone to the Development environment, using your local Git client.

When the push from local to the Development environment has been completed, refresh the Umbraco Cloud portal and you will see that the Development environment is now green, which means that the extraction error has been resolved.

Does your Development Environment still have the red indicator?

The final step is to deploy the pending changes from Development to your Live environment, to ensure everything is completely in sync.

Connect to the database of the Live environment using the .

Sometimes you might need to run another schema deployment on your Cloud environment after deploying to turn your environment green. To do this, follow the steps described in the .

schema deployment guide
Troubleshooting duplicate dictionary items
Video tutorial
Using the error message
Deciding which file you want to use
Getting your environments in sync
Fixing collision errors tutorial
connect to your cloud database locally tutorial
What are UDA files?