> For the complete documentation index, see [llms.txt](https://archivedocs.stackstate.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://archivedocs.stackstate.com/monitors-and-alerts/notifications/troubleshooting.md).

# Troubleshooting

When a notification channel fails to send out notifications the notification overview will show an error status. To inspect the errors:

1. Click on the notification
2. The top of the page shows a banner with a summary of the errors
3. Scroll down to the channels, click on the "error" link for the affected channel(s) to open the error details.

## Common errors

### Slack

Slack errors usually contain an error code:

* `token_revoked`, `token_expired` or `missing_scope`: These error codes all indicate a problem with the authorization of StackState to post messages to Slack. To solve these recreate the channel to re-authorize StackState with Slack such that all required permissions are granted.
* For other error codes see [Slack API error codes](https://api.slack.com/automation/cli/errors).

### HTTP

Most channels, specifically the webhook, expect a HTTP response with status 200 OK. Other responses are considered an error. HTTP errors contain a, usually short, message and the status code that was received instead of 200 OK.

Verify that any configured URLs and tokens are correct and, in case of the webhook, that POST requests are handled properly and return a 200 OK response.

### Other

In case the error is of type "Other" StackState is most likely not able to even connect to the external service or webhook. Verify that URL is correct, can be resolved and can be accessed by StackState.


---

# 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:

```
GET https://archivedocs.stackstate.com/monitors-and-alerts/notifications/troubleshooting.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.