---
schema_version: "1"
id: 2ae642a3e25452273e7bf1f0a05f85947f32101ae54c829c949e52fc6f7c6c33
title: Troubleshoot Metadata Deployment Errors in Experience Cloud Sites
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/experience/264-0-0/networks_migrate_troubleshoot.md
canonical_url: https://help.salesforce.com/s/articleView?id=experience.networks_migrate_troubleshoot.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 2f104d89e0a35ba619416a9b3f0e941f919e4667b4e2bcc1d4b734d9b6c579f3
description: Solve issues that can arise when deploying LWR and Aura sites with ExperienceBundle or enhanced LWR sites with DigitalExperienceBundle.
products:
  - Experiences
release: "264"
---
# Troubleshoot Metadata Deployment Errors in Experience Cloud Sites

Solve issues that can arise when deploying LWR and Aura sites with ExperienceBundle or enhanced LWR sites with DigitalExperienceBundle.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Salesforce Classic and Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Applies to: <a href="https://help.salesforce.com/s/articleView?id=experience.exp_cloud_basics_glossary.htm&amp;type=5&amp;language=en_US" target="_blank">LWR and Aura sites</a></td></tr></tbody></table>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
      <colgroup>
        <col style="width:31.545741324921135%">
        <col style="width:31.545741324921135%">
        <col style="width:36.90851735015773%">
      </colgroup>
      <thead class="slds-text-title_caps ">
        <tr class="">
          <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d41993e79">Error Message</th>
          <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d41993e82">Cause</th>
          <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d41993e85">Solution</th>
        </tr>
      </thead>
      <tbody>
        <tr class="">
          <td data-label="Error Message" class="slds-cell-wrap" style="vertical-align:top;" headers="d41993e79 ">Specify a unique ID for each component in this view.</td>

          <td data-label="Cause" class="slds-cell-wrap" style="vertical-align:top;" headers="d41993e82 ">In DigitalExperienceBundle, each component in a view must have a unique ID. In this
            case, two or more components have the same ID.</td>

          <td data-label="Solution" class="slds-cell-wrap" style="vertical-align:top;" headers="d41993e85 ">
            <p>Retrieve the metadata from both the source and target orgs using
              DigitalExperienceBundle.</p>
            <p>In the view that caused the error, in both the source and the
              target org, search for components with matching IDs.</p>
            <p style="margin-bottom:0;">When you find a matching ID,
              manually update it by altering a couple of characters to ensure that each component has a
              unique identifier.</p>
          </td>

        </tr>
        <tr class="">
          <td data-label="Error Message" class="slds-cell-wrap" style="vertical-align:top;" headers="d41993e79 ">The <samp class="parmname">devName</samp> of an existing route can’t be changed. Revert the
            devName of the <var>generated_route_id</var> route back to its original value and try
            again.</td>

          <td data-label="Cause" class="slds-cell-wrap" style="vertical-align:top;" headers="d41993e82 ">In ExperienceBundle, <samp class="parmname">devName</samp> represents a unique API name that’s
            automatically generated for a route when you create it. <samp class="parmname">devName</samp> is a
            required value that must not be changed. This error occurs if the value was altered in some
            way.</td>

          <td data-label="Solution" class="slds-cell-wrap" style="vertical-align:top;" headers="d41993e85 ">
            <p>Review any recent modifications or customizations related to standard component
              functionality. Determine how and why the name was altered, and revert the name to its
              original value. </p>
            <p style="margin-bottom:0;">Alternatively, consider using SiteDotCom for your deployment instead of
              ExperienceBundle.</p>
          </td>

        </tr>
        <tr class="">
          <td data-label="Error Message" class="slds-cell-wrap" style="vertical-align:top;" headers="d41993e79 ">We couldn't validate <var>property_name</var> in
            <var>file_path</var><samp class="filepath">.json</samp> for component
            <var>component_id</var>. Error: <var>
              specific_error_information</var>
          </td>

          <td data-label="Cause" class="slds-cell-wrap" style="vertical-align:top;" headers="d41993e82 ">In ExperienceBundle, this error occurs when the site configuration in the source org
            doesn't match the target org. For example, let's say the theme in the source org is using
            Default_User_Profile_Menu, but the theme in the target org is using
            Default_User_Profile_Menu1.</td>

          <td data-label="Solution" class="slds-cell-wrap" style="vertical-align:top;" headers="d41993e85 ">Ensure that the sites in the source and target orgs use the same configuration. For
            example, if the specific error information mentions that a component is missing, ensure that
            the component names match in both orgs.</td>

        </tr>
        <tr class="">
          <td data-label="Error Message" class="slds-cell-wrap" style="vertical-align:top;" headers="d41993e79 ">You seem to be missing the property <samp class="parmname">isLockerServiceEnabled</samp> in
            <var>site_name</var><samp class="filepath">/config/mainAppPage.json</samp> with component ID
            <var>component_id</var>.
          </td>

          <td data-label="Cause" class="slds-cell-wrap" style="vertical-align:top;" headers="d41993e82 ">In ExperienceBundle, this error occurs when the
            <samp class="parmname">isLockerServiceEnabled</samp> property in the site's
            <samp class="filepath">config/mainAppPage.json</samp> file is missing.
          </td>

          <td data-label="Solution" class="slds-cell-wrap" style="vertical-align:top;" headers="d41993e85 ">Add <code>"isRelaxedCSPLevel" : false</code> to the
            <samp class="filepath">config/mainAppPage.json</samp> file.
          </td>

        </tr>
        <tr class="">
          <td data-label="Error Message" class="slds-cell-wrap" rowspan="2" style="vertical-align:top;" headers="d41993e79 ">Your site needs a route with route type
            <var>route_type</var>.
          </td>

          <td data-label="Cause" class="slds-cell-wrap" style="vertical-align:top;" headers="d41993e82 ">
            <p>This issue can occur due for various reasons.</p>
            <p>Reason 1: There's a discrepancy between
              the site features or custom objects that are enabled in the source org and the target
              org.</p>
            <p style="margin-bottom:0;">Because of this difference, the ExperienceBundle retrieval process can't include
              the necessary object- or feature-related files from the source org. However, the target org
              requires these files.</p>
          </td>

          <td data-label="Solution" class="slds-cell-wrap" style="vertical-align:top;" headers="d41993e85 ">
            <p>Enable the relevant permission in the source org. Then retrieve ExperienceBundle again
              and deploy the updated bundle to the target org.</p>
            <p style="margin-bottom:0;">If it isn't possible to enable the
              permission in the source org, you can disable the permission on the target org instead. Keep
              in mind that, as a result, permission-related features can be missing in the deployed
              site.</p>
          </td>

        </tr>
        <tr class="">
          <td data-label="Cause" class="slds-cell-wrap" style="vertical-align:top;" headers="d41993e82 ">Reason 2: Each site template includes default routes types that are required. This
            issue can occur if the route type was somehow deleted or renamed.</td>

          <td data-label="Solution" class="slds-cell-wrap" style="vertical-align:top;" headers="d41993e85 ">Update the <var>site_name</var><samp class="filepath">.site-meta.xml</samp> file to
            include a route with the correct route type. Ensure that the route configuration aligns with
            the intended functionality of the site.</td>

        </tr>
      </tbody>
    </table>