Users are troubleshooting issues with Discourse AI’s Semantic Search and Summarization features. Steve_John reports that AI Search is disabled and shows no results, while the Summarize button is missing despite successful backfill jobs. The issue appears to stem from embeddings not being applied to topics, as DiscourseAi::Embeddings::TopicEmbedding.count returns zero. Steve_John resolved the summarization issue related to trust levels but still cannot enable AI Search. Falco suggests checking if DiscourseAi::Embeddings.enabled? is true and reviewing logs for errors. satonotdead shares a NoMethodError related to locale handling, possibly linked to the issue. tobiaseigen asks for a resolution to close the topic.
We’ve successfully configured the Discourse AI plugin using:
LLM Model: gpt-3.5-turbo
Embeddings Model: text-embedding-3-small
We also triggered the background jobs from /sidekiq/scheduler:
Jobs::EmbeddingsBackfill
Jobs::SummariesBackfill
Both completed with a success status. Additionally, the embedding model test returned a successful response.
However, we’re encountering two unresolved issues:
AI Semantic Search:
The AI Search toggle in the search interface remains disabled and cannot be turned on.
The message “Sorry, our AI search found no matching topics” is always shown, despite existing matching content.
AI Summarization:
The “AI Summary” button or output is not visible on any topic page, even though all summarization-related settings and the persona are correctly enabled.
The AI Helper (composer assistant) works as expected, but AI Search and AI Summarization features (Summarize button not visible) remain inactive, likely due to embeddings not being applied to existing topics despite backfill jobs reporting success.
We managed to resolve the Summarize issue—it turned out to be related to trust level settings. However, we’re still facing trouble with the AI Search feature. Specifically, we’re unable to toggle the button to enable AI.
We attempted to activate it manually via the backend using the following command:
ruby
CopyEdit
DiscourseAi::Embeddings::CreateEmbeddings.new(model: "text-embedding-3-small").embed("This is a test")
Then we checked the embedding count with:
ruby
CopyEdit
DiscourseAi::Embeddings::TopicEmbedding.count
Unfortunately, the count remains zero, indicating that embeddings aren’t being created, even when triggered manually. We also tried rebuilding the AI plugin, suspecting that some files might not have been properly updated—but the issue persists.