Slack channel missing from LangSmith alert destination picker

Last updated: November 20, 2026

Symptom

When configuring a Slack destination for a LangSmith Alert, a channel you expect to see doesn't appear in the Slack channel picker. Searching for it shows No channels found, even though the channel exists in Slack and, in some cases, the LangSmith Slack app has already been added to it. On large Slack workspaces (many thousands of channels), clicking the picker's refresh icon can also show Slack rate limits hit — try again later.

Cause

The channel picker lists channels from each Slack workspace linked to your LangSmith organization: all public channels, plus private channels the LangSmith app has been invited to. LangSmith saves this list and refreshes it in the background about once an hour. A channel can be missing for a few reasons:

  • The channel belongs to a different Slack workspace than the one(s) linked to your LangSmith organization. An organization can be linked to multiple Slack workspaces.

  • The channel is private and the LangSmith Slack app hasn't been invited to it. (Public channels do not need the app invited to be listed.)

  • The channel was created, renamed, or made public recently, and the saved list hasn't refreshed yet.

  • On workspaces with many thousands of channels, loading the full list from Slack takes many requests and can hit Slack's rate limits. When that happens LangSmith keeps showing the previously saved list and finishes loading in the background, so a recently changed channel may not appear for a while.

Note: when you type in the search box, any workspace with no matching channels is hidden, including its "Slack rate limits hit" notice. No channels found can therefore mean the list is still loading, not that the channel is inaccessible.

Resolution

Work through these checks in order:

  1. Open the Channel dropdown with the search box empty. Each linked Slack workspace appears as a heading, along with any notice such as "Slack rate limits hit — try again later." Confirm the channel lives in one of those workspaces. If it doesn't, click Link another Slack workspace… and approve the workspace that has the channel.

  2. If the channel is private, invite the LangSmith Slack app to it (for example, run /invite @LangSmith in the channel).

  3. Click the refresh icon in the search box once to load the latest channel list. If you see "Slack rate limits hit", don't keep clicking; each click asks Slack for the full list again. Wait a few minutes, reload the alert page, and search again.

  4. If the channel still doesn't appear, route the alert to the channel through a Slack Workflow Builder webhook instead of the native Slack destination. This bypasses the channel picker entirely and works for any channel the workflow can post to. See Routing LangSmith Alerts to Slack.

If you'd like us to investigate why the channel is missing from the picker, contact LangChain support with your LangSmith workspace URL, the Slack channel ID (in Slack, click the channel name and open About; it starts with C), and the approximate time you tried, including time zone.

References