Retrain knowledge
Refresh eligible website and Notion knowledge after its source material changes.
Retraining refreshes the sources that can change outside AgentStack. It is not a universal re-index button. A retrain processes completed website sources and enabled Notion sources. Uploaded files and Q&A pairs are indexed when you upload or edit them, so they are not included in a retrain.
Start a manual retrain
Open Sources → Auto-Retrain and select Retrain Now. Manual retraining is available from Standard and above, and AgentStack serializes retrains for one agent, so it rejects a second request while another retrain is already started. The confirmation means the work has been queued; use the history table to see its terminal result.
What changes
For websites, AgentStack re-crawls with the current plan’s page limit and the source’s saved include and exclude patterns. New or changed content is embedded; content whose hash has not changed can be recorded as unchanged; pages that disappear can be removed. For Notion, enabled pages are refreshed when their remote edit time changes.
This means a manually added Page is not necessarily refreshed as one URL forever. It is stored under a website grouping, and a later retrain may rediscover from that grouping URL. Keep the source boundary narrow if that behavior matters.
Read retrain history
The Retrain History table shows the date, status, trigger, pages crawled, changed pages, unchanged pages, and duration. Statuses include started, completed, partial, and failed. A partial result is not the same as a full success; inspect the source set and retest the facts you changed before treating it as ready.
For scheduled refreshes, use Auto-Retrain. For initial ingestion, start with website crawls or Notion sources.