Recipe import fails : The configuration name "canvas.folder.xxxxx" does not match the ID "xxyyzz"
>>> [!note] Migrated issue
<!-- Drupal.org comment -->
<!-- Migrated from issue #3556831. -->
Reported by: [pritishkumar](https://www.drupal.org/user/3520580)
Related to !671
>>>
<h3 id="summary-problem-motivation">Problem/Motivation</h3>
<p>While testing the site export/import feature in Drupal CMS 2.0 alpha, a configuration import error occurs related to canvas.folder.* configuration entities.</p>
<p>After exporting a site as a recipe and attempting to install a new site using that recipe, the import fails with a UUID mismatch error in one or more canvas.folder.* configuration files.</p>
<p>The error message displayed is:</p>
<pre>The configuration name "canvas.folder.06eb65b4-91b4-4825-9c7c-cd8de29791cb" does not match the ID "912cd7bd-655e-4384-8441-2ecb4ce6b60d"</pre><p>This suggests that the exported recipe is including configuration files where the filename UUID and the internal uuid value differ, preventing successful import.</p>
<h4 id="summary-steps-reproduce">Steps to reproduce</h4>
<ul>
<li>
<li>Install Drupal CMS 2.0 alpha.</li>
<li>Install the Drupal CMS Starter Kit (which includes the default 404 and Privacy Policy pages).</li>
<li>Make a small edit to the 404 page (for example, change a line of text).</li>
<li>Use the Site Export feature to export the site as a recipe.</li>
<li>Attempt to install a new site using the exported recipe.</li>
<li>Observe the configuration import error related to canvas.folder.* entities during the site install process.</li>
</ul>
<p>Note: I had to also use the patch from<br>
<a href="https://www.drupal.org/project/canvas/issues/3550165#comment-16324441">https://www.drupal.org/project/canvas/issues/3550165#comment-16324441</a><br>
as it was not allowing me to save the content change made to the 404 page.</p>
<h3 id="summary-proposed-resolution">Proposed resolution</h3>
<h3 id="summary-ui-changes">User interface changes</h3>
<h3 id="summary-data-model-changes">Configuration changes</h3>
issue