{"section":"known-issues","requestedLocale":"en","requestedSlug":"configuration-blocks-default-routes-in-other-bindings-on-rewriter-can-lead-to-not-found-page-after-applying-filters","locale":"en","slug":"configuration-blocks-default-routes-in-other-bindings-on-rewriter-can-lead-to-not-found-page-after-applying-filters","path":"docs/en/known-issues/Store Framework/configuration-blocks-default-routes-in-other-bindings-on-rewriter-can-lead-to-not-found-page-after-applying-filters.md","branch":"main","content":"## Summary\n\n\nThis issue only occurs in cross-border stores. When applying certain filters on a search page, the page breaks and redirects to a \"Not Found\" page. The issue is caused by the configuration \"Blocks default routes in other bindings\" in the Rewriter app.\n\n\n#### Simulation\n\n\n\n1. Access the search page of a cross-border store.\n2. Apply one or more specific filters.\n3. Observe that when trying to load the results, the page redirects to a \"Not Found\" page.\n\n\n#### Workaround\n\n\nSetting the `preventRouteChange` property to `true` in the Search Result component prevents the issue from occurring."}