Issue
The Slack connector is configured and authenticated correctly, but no messages are indexed from the specified Slack channel, even though user profiles are successfully retrieved. The issue persists when using the channel ID in the configuration.
Diagnosis
This issue typically occurs when the Slack connector configuration is incomplete or incorrect. To confirm this issue:
Verify that user profile data is being indexed, but channel messages are not.
Confirm that the target channel is public and accessible.
Ensure the channel is listed in the connector configuration either by name or ID.
Confirm that API access (e.g.,
conversations.history) is working when tested externally, indicating sufficient OAuth permissions.
If all the above checks are positive and messages are still not being indexed, continue to the resolution steps.
Environment
Fusion 5.9.14
Slack connector v2
Applicable to Self Hosted and Lucidworks Hosted Setup.
Cause
The Slack connector requires specific configuration settings to successfully index messages from channels. If the connector is provided a channel ID instead of the channel name, and indexing of public channels is not explicitly enabled, messages may not be retrieved. Additionally, if the “Index channels” setting is disabled, message ingestion will fail silently.
Resolution
To resolve this issue, review and apply the following configuration updates to the Slack data source:
Enable indexing for channels
In the data source settings for the Slack connector, navigate to Channels and messages settings.
Ensure the Index channels checkbox is enabled.
Enable public channel indexing
Ensure the Index from public channels option is enabled in the connector configuration.
Use the channel name instead of the channel ID
In the Channels to include field, enter the name of the channel (e.g.,
general) rather than the Slack channel ID (e.g.,ABC1011LPQW).Save the configuration and rerun the data source.
Enable diagnostic logging (optional)
If indexing still fails after verifying the above steps, enable Diagnostic logging to gather more detailed information from the connector logs.
Once these guidelines are followed, messages should begin indexing as expected.