{"section":"known-issues","requestedLocale":"en","requestedSlug":"some-custom-pages-are-not-returning-in-custom-routes-api-causing-missing-entries-in-the-sitemap","locale":"en","slug":"some-custom-pages-are-not-returning-in-custom-routes-api-causing-missing-entries-in-the-sitemap","path":"docs/en/known-issues/Store Framework/some-custom-pages-are-not-returning-in-custom-routes-api-causing-missing-entries-in-the-sitemap.md","branch":"main","content":"## Summary\n\nIn stores with a high volume of routes registered in the Rewriter, some custom pages don't appear in the Custom Routes API (`/_v/public/sitemap/custom-routes`) response and are missing from the generated sitemap. The generation process has a scan limit and can stop before reading all routes when the account has a large number of stale/expired entries, causing some valid pages to be silently skipped.\n\n## Simulation\n\n- Identify an account with a high volume of routes registered in the Rewriter.\n- Call the Custom Routes API and confirm some known custom pages are missing from the response.\n- Access the sitemap generated for the store and confirm the same pages are also absent there.\n\n## Workaround\n\nN/A"}