Discourse AI - Semantic Search & Summarization Not Working for our configuration

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:

  1. 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.
  1. 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.

Have you enabled ai_summarization_enabled and ai_embeddings_semantic_search_enabled? Are there any issues showing up in /logs ?

Hi Sam,

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.

  1. Is DiscourseAi::Embeddings.enabled? true?

  2. If yes, there should be an error in the /logs page.