> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-server/2025.6/instance-administration/system-functions/notifications/slack/troubleshooting.md).

# Troubleshooting the Slack connection

How to troubleshoot various issues with your Slack connection in SonarQube Server 2025.6.

## User is stuck in the Connect > Already Bound loop

The SonarQube Server app for Slack blocks the user from subscribing by asking every time to subscribe. This may happen if your organization uses Slack Enterprise and the app has been installed on your workspace via a `@SonarQube Server` command or directly from the Slack app configuration page (This is possible if the app is already installed on another enterprise’s workspace). The SonarQube Server app for Slack must be installed directly through SonarQube Server otherwise it won’t work properly. To fix this:

1. Uninstall the app from your Slack workspace.
2. In SonarQube Server, install the app in your workspace as described in [Setting up the connection to Slack](/sonarqube-server/2025.6/instance-administration/system-functions/notifications/slack/setup.md#multiple-workspaces).


---

# 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.sonarsource.com/sonarqube-server/2025.6/instance-administration/system-functions/notifications/slack/troubleshooting.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.