> 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-agentix/configure-cortex-agentix/remote-repository-management/remote-repository-troubleshooting.md).

# Remote repository troubleshooting

Troubleshoot Cortex AgentiX remote repository setup, branch conflicts, and repository type changes.

The following scenarios can occur when managing the remote repository.

### **Pointing to a non-empty branch when enabling a tenant**

If you configure a tenant to use a remote repository, you have two 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 content from the tenant, you must use an empty branch. If the branch is not empty, you will get an error message prompting you to select an empty branch. Alternatively, you can select the first option and overwrite all content in the tenant with the content from the remote repository.

### **Switching between remote repository types**

If you switch between built-in and private remote repository types, you get a warning that switching between repository types may result in the loss of all version history.

To keep your content history, select **Existing content on your tenant** to overwrite all content in the remote repository with content from your tenant.


---

# 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-agentix/configure-cortex-agentix/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.