> For the complete documentation index, see [llms.txt](https://help.sleuth.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sleuth.io/sleuth-dora/integrations-1/fixing-broken-integrations.md).

# Fixing broken integrations

Sleuth proactively checks for broken integrations and, when it finds them, displays a warning icon in the top navigation.

<figure><img src="https://2832637360-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1bR_-Od0islbiOl4G0%2Fuploads%2FwK2bRNhDnNizS9qm7D5e%2Fimage.png?alt=media&amp;token=d95669f0-03a9-48a6-bf21-ecd933fb8ca0" alt=""><figcaption></figcaption></figure>

The warning icon links to a global **Needs attention** page that lists any broken integrations that Sleuth detects along with instructions on how to resolve them.

<figure><img src="https://2832637360-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1bR_-Od0islbiOl4G0%2Fuploads%2FDwPg7nL15ic35KfoYJGs%2Fimage.png?alt=media&amp;token=47b71779-f198-4e0b-955a-7f049495a114" alt=""><figcaption></figcaption></figure>

Sleuth continuous to automatically check connections, and once a previously identified connection issue appears to have been resolved, Sleuth removes that item from the **Needs attention** screen.


---

# 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://help.sleuth.io/sleuth-dora/integrations-1/fixing-broken-integrations.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.
