Retrain knowledge
Refresh eligible website and Notion knowledge after its source material changes.
Retraining refreshes the sources that can change outside AgentStack. It does not re-index every source. A retrain processes completed website sources and enabled Notion sources. AgentStack indexes uploaded files and Q&A pairs when you upload or edit them. A retrain does not include them.
Start a manual retrain
Open Sources → Auto-Retrain and select Retrain Now. Manual retraining is available on the Standard plan and above. AgentStack runs one retrain per agent at a time, so it rejects a second request while a retrain is in progress. The confirmation shows that AgentStack queued the work. Check the history table for the final result.
What changes
For websites, AgentStack re-crawls with the current plan's page limit and the source's saved include and exclude patterns. AgentStack embeds new or changed content. Content with an unchanged hash can stay marked as unchanged. AgentStack can remove pages that no longer exist. For Notion, AgentStack refreshes enabled pages when their remote edit time changes.
A manually added Page does not always stay as one URL forever. AgentStack stores it under a website grouping, and a later retrain can rediscover it from that grouping URL. If that behavior matters, keep the source boundary narrow.
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. Before you treat a partial result as ready, inspect the source set and retest the facts that you changed.
For scheduled refreshes, use Auto-Retrain. For initial ingestion, start with website crawls or Notion sources.