Re-indexing and usage
Re-index a source
Indexing starts automatically when you add a plain text, website, file, or YouTube source. Re-indexing is manual: click Index in the source's row when:
- The status is Modified — the source changed after its last indexing, and agents still answer from the previously indexed version.
- The status is Error — fix the cause, for example page access or video availability, then retry.
- A web page changed since the last fetch — website sources stay Ready and are not re-fetched automatically.
While a source is indexing, the row action changes to Stop indexing. A stopped source returns to Modified, so you can index it again later. Statuses update on the open page as indexing progresses — you don't need to refresh.
FAQs have no Index action: Q&A pairs are indexed as soon as you add or edit them. While a FAQ is being processed — for example, right after Auto-generate from File — its card shows Indexing... in place of the Q&A count.
Track source usage
Usage Count shows whether a source actually contributes to answers. The count grows each time an agent uses the source in a reply and updates in real time while the page is open. On this page, counts are totals across all agents; on the agent page, the same column counts that agent's usage only. On the FAQs tab, usage is tracked per Q&A pair, so you can see which exact answers fire.
Sort any table by Usage Count to see which sources carry your conversations — review those first when content changes — and which stay at 0 because they are not connected, not indexed, or cover questions customers never ask.
For Q&As in a FAQ connected with Vector Search disabled, the agent page shows Not available instead of a number: the entire FAQ is included in the agent's prompt, and usage is not tracked. See Set the Vector Search mode for FAQs.