> For the complete documentation index, see [llms.txt](https://developer.kizen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.kizen.com/docs/integrations-and-plugins/integrations/slack-beta/troubleshoot-slack.md).

# Troubleshoot Slack

{% hint style="success" %}
**Audience:** Admins, Developers, Solution Architects

**Purpose:** Describes troubleshooting methods for issues with the Stack integration in <code class="expression">space.vars.Kizen\_company\_name</code>
{% endhint %}

The following table presents solutions to common issues with the Slack integration. For additional help, see the [Slack developer docs](https://docs.slack.dev/).

| Issue                                                | Cause                                                                                                             | What to do                                                                             |
| ---------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- |
| A message failed with the `channel_not_found` error. | The channel doesn't exist, or it does exist but it's private.                                                     | Confirm the channel exists. If it's a private channel, run `/invite @Kizen` inside it. |
| A plain-text message was truncated.                  | The message exceeded 40,000 characters.                                                                           | Reduce the length of the message.                                                      |
| A block message wasn't posted.                       | The JSON objects that make up the blocks might be malformed, or the blocks might exceed Slack's character limits. | Review the blocks, and try again.                                                      |
| You no longer have a connection to the Slack API.    | The access token is no longer valid.                                                                              | Re-authenticate the integration.                                                       |

***

## What's Next

See [Slack - Beta](/docs/integrations-and-plugins/integrations/slack-beta.md) for a high-level discussion about what the Slack integration is and how it works.&#x20;

<details>

<summary><strong>Related Topics</strong></summary>

* [Slack - Beta](/docs/integrations-and-plugins/integrations/slack-beta.md)
* [Set Up Slack in Kizen](/docs/integrations-and-plugins/integrations/slack-beta/set-up-slack-in-kizen.md)
* [Use Slack in an Agentic Workflow](/docs/integrations-and-plugins/integrations/slack-beta/use-slack-in-an-agentic-workflow.md)

</details>

***

*Slack is a registered trademark and service mark of Slack Technologies, Inc. Kizen's Slack integration is not created by, affiliated with, or supported by Slack Technologies, LLC.*


---

# 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://developer.kizen.com/docs/integrations-and-plugins/integrations/slack-beta/troubleshoot-slack.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.