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

# Troubleshooting

Use the integration status and latest sync-history entry before changing a credential or network policy.

## Configuration required

The provider is installed but one or more required fields are empty. Compare the form with the provider guide and keep credentials in secret fields.

## Authentication or authorization failure

1. Confirm the credential has not expired or been revoked.
2. Verify the required provider scopes and organization access.
3. Check SSO or administrator approval requirements.
4. Rotate the credential if it was exposed.
5. Save the new secret and run another sync.

## Network, DNS, or TLS failure

1. Resolve the provider hostname from the Kangal worker environment.
2. Confirm outbound TCP 443 is allowed.
3. Check trusted certificate authorities and TLS interception rules.
4. Verify proxy, firewall, and Kubernetes NetworkPolicy settings.
5. Confirm custom endpoints use approved HTTPS origins.

## Rate limiting

Kangal records provider rate-limit and `Retry-After` metadata when available. Wait for the retry window, reduce sync frequency, or request a higher provider limit. Do not create multiple credentials solely to bypass provider controls.

## Sync remains pending

1. Check worker health and Redis connectivity.
2. Inspect retry and dead-letter status.
3. Confirm the provider endpoint is reachable from the worker.
4. Replay only after correcting the underlying cause.

## Escalation evidence

Provide the Kangal sync ID, timestamp, provider slug, normalized error category, and provider request ID. Never include plaintext credentials in support data.


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.kangal.dev/integrations/troubleshooting.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.