Why isn't Yaplet answering from a source I added?

Updated August 13, 2026

Start on one screen

You added an article, or a file, or a page of your site — and the AI still says it does not know. Almost every time, the answer is on Brand → Knowledge: each source row tells you whether your brand actually stored anything from it, and it takes about ten seconds to check.

The statuses

Rows for websites, files, text snippets and questions and answers carry a status badge:

  • Ready — stored and searchable. This is the one you want.
  • Not indexed — nothing was stored from it, so Yaplet cannot answer from it at all. Hover it: "Nothing was stored from this, so Yaplet cannot answer from it yet." Usually an empty file, or a page that could not be read.
  • Reading… — we are still working through it. Wait a little and refresh.
  • Failed — files, text snippets and questions and answers only: the last attempt to store it did not succeed. Hover the status to see why.
  • Warning — read, but not cleanly. Hover for the reason.
  • Stopped — websites only: the site's list of pages could not be read for 14 days, so the hourly checks stopped. Yaplet keeps answering from what it learned.

Once a group has more than ten rows, a search box and a status filter appear above it, and a group with a source that needs attention opens by itself and says so in its header. If a website has stopped after repeated failed reads, a notice also tells you as the page opens: "Some sources need attention".

Pieces indexed

The line of facts under each source's name says how many searchable pieces Yaplet stored from it — for example 12 pieces indexed — and the Indexed figure in the summary at the top adds them all up. Longer sources become more pieces; one article is usually several. Not indexed (Not indexed yet on a knowledge base or documentation row) means nothing was stored, which is the same bad news as the status.

Two things to know. On a knowledge base or documentation set the count includes only published articles and pages. And for a website, file, text snippet or question and answer you can see exactly what was kept: choose See what was stored in the row's menu (for a website, in Manage pages).

The most common cause: it is still a draft

A draft is invisible to the AI. Publishing an article indexes it immediately — no chatbot required, no widget required, nothing to sync. Unpublishing removes it again just as quickly. If the Indexed number on a knowledge base is lower than the number of articles you think you wrote, some of them are drafts.

The second most common cause: nothing can pay for learning right now

Yaplet only learns or refreshes website pages, files, text, questions and answers and product feeds when something can pay for it: your free 14 days, credit you bought, or a paid plan. If none can, nothing new is learned, the summary at the top of the Knowledge page says "Paused until you add credit or choose a plan" next to Website last read, and nothing Yaplet already learned is removed. Older free workspaces that still have free monthly answers have a different limit: 250 searchable pieces across the whole workspace, shown as "212 of 250 on the free plan", and when it is full the page says "Your free plan's knowledge is full". Remember that one article is usually several pieces, so 250 is not 250 articles. And if a website row says "You've reached your knowledge limit", use Write to us on that row.

If the AI still quotes an article

If the AI still quotes an article you expected to be gone, that article is still published somewhere in this brand's knowledge, so look for it there.

When a website failed

Hover the Warning or Stopped status for the reason. To try again, choose Check now in the website row's menu. A website can only be checked once every five minutes, and if one is already being read you will be told to wait for it to finish. To see which pages Yaplet learned, why a page failed, and to switch some of them off, press Manage pages on the row.

If everything says Ready and it still does not answer

Then the content reached the AI and the problem is somewhere else. Three things worth checking: is the AI agent switched on (Brand → AI agent → General, Enable Yaplet); is its Answers on switch for that channel on, in the same section; and is it set to decline rather than answer when it is unsure (Human hand-off section, When Yaplet has no answer)? Beyond that, a question phrased very differently from your content is a knowledge gap, not a broken source.

Next step

Find the gaps that keep coming back, and what to write for them: Find knowledge gaps Yaplet couldn't answer. Adding something new: Add knowledge to your brand.

Did this article answer your question?