> For the complete documentation index, see [llms.txt](https://docs.hivel.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hivel.ai/faqs/pr-issues-and-workflow-faqs/why-some-of-the-repositories-are-not-imported-or-synced.md).

# Why some of the repositories are not imported or synced?

Sometimes, you might notice that certain repositories are listed as **not synced** in Hivel. This can happen due to the following reasons:

1. **Lost Access**: Hivel no longer has access to the workspace or repository due to expired or revoked token permissions.
2. **Inactivity**: The repository hasn’t had any recent activity, so no new data has been synced.

#### Steps to Fix Unsynced Repositories

To resolve this issue:

1. **Reauthorize Hivel**: If access has been lost, reauthorize Hivel with the necessary permissions to the workspace or repository. This will restore synchronization and ensure data is up to date.
2. **Check Repository Activity**: For inactive repositories, verify if they are expected to remain dormant or should have recent updates.

If you need further help, please contact our support team at [<mark style="color:purple;">support@hivel.ai</mark>](mailto:support@hivel.ai).

{% content-ref url="/pages/Dp16Ail2s2tNgvdCuUHm" %}
[How to reauthorize Github with a classic token?](/archive/github/alternate-methods/how-to-reauthorize-github-with-a-classic-token.md)
{% endcontent-ref %}

{% content-ref url="/pages/B3i4PL0CQpDgtI2K183z" %}
[Broken mention](broken://pages/B3i4PL0CQpDgtI2K183z)
{% endcontent-ref %}

{% content-ref url="/pages/HBpnA0FItXHWrrOhMExz" %}
[Broken mention](broken://pages/HBpnA0FItXHWrrOhMExz)
{% endcontent-ref %}

{% content-ref url="/pages/liBYbL1h8aoUlrxiF4m6" %}
[GitLab](/integrations/version-control/gitlab.md)
{% endcontent-ref %}


---

# 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://docs.hivel.ai/faqs/pr-issues-and-workflow-faqs/why-some-of-the-repositories-are-not-imported-or-synced.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.