> For the complete documentation index, see [llms.txt](https://search.docs.reactify.com.au/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://search.docs.reactify.com.au/troubleshooting/further-troubleshooting.md).

# Further Troubleshooting

Even with documentation available it’s common to run into issues during implementation that are unclear or confusing. A quick process for debugging any issue that is causing confusion is to remove all custom code and simply let the Reactify Search package render out the default components.

To do this find the [ReactifySearchProvider component](/components/provider.md) that's experiencing issues, set the necessary props, disable any custom code and insert the [Sensors](/components/sensors.md), [Filters](/components/filters.md) and [Results](/components/results.md) components within.

```tsx
import React from "react";
import { ReactifySearchProvider, Sensors, Filters, Results } from "@usereactify/search";

export const CustomPage: React.FC = () => (
  // <CustomStuff ...>
    <ReactifySearchProvider
      mode="search"
      shopifyPermanentDomain="usereactify-demo.myshopify.com"
    >
      <Sensors />
      <Filters />
      <Results />
      // <CustomStuff ... />
    </ReactifySearchProvider>
  // </CustomStuff>
);
```

If the default components **do render** correctly the issue is most likely somewhere deeper within the custom components. You can now start adding those components back one-by-one until the issue reappears, at the very least this should help locate the problematic components.

If the default components **do not render** correctly it’s possible there is an issue with the props provided to the [ReactifySearchProvider component](/components/provider.md) or alternatively there might be a configuration issue.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://search.docs.reactify.com.au/troubleshooting/further-troubleshooting.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.