> For the complete documentation index, see [llms.txt](https://broadcast.presidiocreative.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://broadcast.presidiocreative.com/collections/collection-pages/sub-collections/subcollections-troubleshooting-checklist.md).

# Subcollections - Troubleshooting checklist

The main thing to look out for when setting up your subcollections is to always check if the menu handle is the same as the collection handle.

If the handles are different, then you won't be able to see the subcollections when customizing/previewing the theme.

<figure><img src="/files/mXI0mITkV6nReansELpm" alt="Image is pointing where exactly the collection handle is placed"><figcaption></figcaption></figure>

<figure><img src="/files/509PD4yRAHxtkxFdTgGj" alt="Here it&#x27;s pointed out where the menu handle is located"><figcaption></figcaption></figure>

Another less common issue when setting subcollections is making sure that your first layer's menus have a link to the collections that you wish to display in the subcollection section.

<figure><img src="/files/GHX6JDFpWewFOapTpmYV" alt="Pointing where to edit the collection links"><figcaption></figcaption></figure>


---

# 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://broadcast.presidiocreative.com/collections/collection-pages/sub-collections/subcollections-troubleshooting-checklist.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.