{"section":"known-issues","requestedLocale":"en","requestedSlug":"custom-sitemap-saveindex-returns-entity-not-found-on-the-final-domain","locale":"en","slug":"custom-sitemap-saveindex-returns-entity-not-found-on-the-final-domain","path":"docs/en/known-issues/Store Framework/custom-sitemap-saveindex-returns-entity-not-found-on-the-final-domain.md","branch":"main","content":"## Summary\n\nStores that use the `saveIndex` feature to generate custom sitemaps (URLs in the format `/sitemap/{index-name}.xml`) may get an \"Entity not found\" error when accessing these files through the final production domain, even though the master index (/sitemap.xml) is updated correctly. The same file still works normally on `*.myvtex.com`. The issue is related to a routing difference between the two domains, which causes the custom index to not be recognized correctly on the final domain.\n\n## Simulation\n\n- Have an account that uses the `saveIndex` feature to register a custom sitemap index (e.g., `myindex`), associated with the production binding.\n- Access `https://{accountName}.myvtex.com/sitemap/myindex.xml` → returns 200.\n- Access `https://{final-domain}/sitemap/myindex.xml` → returns \"Entity not found\" error.\n- The master index `sitemap/custom-user-routes-1.xml` lists the entry correctly on both domains, indicating that only the child file read fails on the final domain.\n\n## Workaround\n\nThe affected store must open a support ticket requesting the workaround, which will be applied on a per-account basis"}