> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kombo.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Issues

> See which integrations need attention, and how long the problem has been going on.

When an integration starts failing, you want to know about it before your customer does. Issues put those problems on the dashboard as soon as Kombo observes them, so you can act before the end customer complains.

<Frame>
  <img src="https://mintcdn.com/kombo/GsgKLLm-Oedz8M_n/images/issues/integrations-list.jpg?fit=max&auto=format&n=GsgKLLm-Oedz8M_n&q=85&s=251330c4dab02cc99acdd78b91cd0d5b" alt="Issues column on the integrations list" width="1800" height="799" data-path="images/issues/integrations-list.jpg" />
</Frame>

The integrations list shows an issue count on any integration that currently has an open issue. Hover the count to see the title and how long Kombo has been observing it.

Open the integration to read what is wrong and what to do next.

<Frame>
  <img src="https://mintcdn.com/kombo/GsgKLLm-Oedz8M_n/images/issues/integration-page.jpg?fit=max&auto=format&n=GsgKLLm-Oedz8M_n&q=85&s=b65c1a6783bd4fc71a6e339b89daad7c" alt="Issue details on an integration" width="1800" height="590" data-path="images/issues/integration-page.jpg" />
</Frame>

## What an issue is

Kombo's issues track a problem of an integration over time. Kombo raises them when a condition is true (for example, authentication is failing) and keeps it open while that condition is still observed. When the condition clears, the issue resolves on its own.

Each issue tells you:

* what is broken
* how to investigate or fix it
* when Kombo first observed it, and when it last saw it again

As we are rolling out issues, more types will follow.

## What to do when you see one

1. Open the integration from the list.
2. Read the issue. Follow the linked [logs](./logs) if you need the underlying requests.
3. If credentials are invalid, [reconnect the integration](../guides/connect/reconnection).

The [integration state](../guides/integration-states) on the same page is the current snapshot (`Active`, `Sync failing`, `Authentication failing`). The issue is the durable record that the problem is still happening, and for how long.

You can snooze an issue to hide it in the Kombo dashboard for a while. Snoozing only affects the UI. The issue stays open, Kombo keeps observing it, and it does not send an [`issue-status-changed`](../guides/webhooks#issue-status-changed) webhook.

Subscribe to that webhook to get raised and resolved events as they happen. Slack notifications will follow.

<CardGroup cols={2}>
  <Card title="Logs" icon="scroll" href="./logs">
    Inspect the requests behind a failing sync or action.
  </Card>

  <Card title="Reconnecting" icon="arrow-rotate-right" href="../guides/connect/reconnection">
    Restore credentials when authentication has failed.
  </Card>

  <Card title="Integration states" icon="traffic-light" href="../guides/integration-states">
    Read the current operational status of an integration.
  </Card>

  <Card title="Webhooks" icon="webhook" href="../guides/webhooks#issue-status-changed">
    Get raised and resolved issue events as they happen.
  </Card>
</CardGroup>