> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/remote-repository-management/remote-repository-troubleshooting.md).

# Remote repository troubleshooting

Troubleshoot Cortex XSIAM remote repository issues, including non-empty branches and switching between built-in and private repositories.

Use this guide to resolve common Cortex XSIAM remote repository configuration issues. These issues include non-empty Git branches and repository type changes.

### Resolve non-empty branch errors when enabling a tenant

When you configure a Cortex XSIAM tenant to use a remote repository, choose one of these options:

* Overwrite all content in the tenant with content from the repository.
* Overwrite all content in the remote repository with content from the tenant.

To overwrite the remote repository with tenant content, use an empty branch. A non-empty branch produces an error that prompts you to select an empty branch. Alternatively, overwrite tenant content with content from the remote repository.

### Switch between built-in and private remote repositories

Switching between built-in and private remote repository types can remove version history. Cortex XSIAM displays a warning before you make the change.

To retain content history, select **Existing content on your tenant**. This overwrites remote repository content with tenant content.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/remote-repository-management/remote-repository-troubleshooting.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.