{"section":"known-issues","requestedLocale":"en","requestedSlug":"rewriter-is-not-receiving-url-updates","locale":"en","slug":"rewriter-is-not-receiving-url-updates","path":"docs/en/known-issues/Store Framework/rewriter-is-not-receiving-url-updates.md","branch":"main","content":"## Summary\n\n\nWhen a URL is changed/deleted on the catalog, the rewriter does not receive this change. Since the rewriter is not notified about it, the URL is still pointing to the wrong type, which can also lead to problems on the IS.\n\nThis can also happen when creating new category/subcategory routes on the catalog. The rewriter sometimes will need you to run the bootstrap query to receive those routes.\n\n\n##\n\n## Simulation\n\n\nTry deleting an existing brand from the catalog\nRun the mutation to see how this path is being received on the rewriter\n\n    \\{internal\\{ get(path:\"/brand\")\\{   from   declarer   query   disableSitemapEntry \\}\\}\\}\n\nIf you look for that brand on the storefront, it will still be pointing to a `map=b`\n\nYou can also check how this path is being returned on the pageType; if it is a fullText, the pageType was updated, and the rewriter didn't.\n\n\n##\n\n## Workaround\n\n\nTry deleting the route manually from the rewriter:\n\n    mutation\\{ internal\\{   delete(path:\"/path\")\\{     from     id     resolveAs   \\} \\}\\}\n\n\nTry running the bootstrap query to update the rewriter:\n\n    \\{bootstrap \\{ brands categories\\}\\}"}