> For the complete documentation index, see [llms.txt](https://docs.openiam.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openiam.com/troubleshooting/connectors.md).

# Synchronization and connectors

Synchronization runs, the connector source they read through, and where the per-connector pages are.

Synchronization reads from a source and hands what it finds to provisioning; where that source is a managed system, it reads through a connector. The two fail in different places, and telling them apart early saves most of the work.

**Most connector troubleshooting lives with the connector itself.** Every connector page in [Connector configuration](/connector-configuration/connectorconfig.md) ends with its own symptom table, which is the place to start when one target system misbehaves.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Troubleshooting a synchronization run</strong></td><td>A run that will not start, runs and imports nothing, or imports the wrong thing.</td><td><a href="/troubleshooting/connectors/synchronization-runs.md">Troubleshooting a synchronization run</a></td></tr><tr><td><strong>The synchronization source</strong></td><td>What the connector source does, and an old configuration set to a value that no longer exists.</td><td><a href="/troubleshooting/connectors/sync-vs-async-source.md">The connector synchronization source</a></td></tr><tr><td><strong>General connector troubleshooting</strong></td><td>Steps that apply to any connector — the queue, the managed system, the connector service itself.</td><td><a href="/connector-configuration/4-troubleshootingconnector.md">Provisioning operations troubleshooting</a></td></tr></tbody></table>


---

# 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.openiam.com/troubleshooting/connectors.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.