# Git Sync status shows an unexpected error

### When I was merging a change request from GitBook

Please try creating a new change request in GitBook with a small change, such as adding a word or space somewhere in your documentation. Merging this change request should retrigger sync and GitBook will export your content again.

When doing this new export, all content will be exported again, including the previous sync where the error happened.

### When I was merging a commit from GitHub/GitLab

Please try creating a new commit in your repository with a small change, such as adding a word somewhere in your documentation. When this commit is merged, GitBook will attempt to import your content again as the sync process will be retriggered.

When doing this new commit, all content from your repository will be imported again, including the previous sync where the error happened.

### When I was trying to set up Git Sync for the first time

Please remove the integration you are using (GitLab or GitHub) and enable it again in your space. Please go through the setup process one more time.

If the steps mentioned above do not prove to be helpful, kindly get in touch with our support team.


---

# Agent Instructions: 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:

```
GET https://gitbook-open-v2-preview.gitbook.workers.dev/url/gitbook.com/docs/help-center/integrations/integrations-troubleshooting/git-sync/git-sync-status-shows-an-unexpected-error.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.