How a refresh compares rows, the freshness badges, refreshing on a schedule, the Add to knowledge base pipeline step, and Ask Greg's proposals. Refreshing a source compares every row with what was added before, by a hash of its content. Unchanged rows are not sent to the model again, so refreshing a large source that has not changed costs nothing. A row that changed is added as a new version and the old chunk is marked outdated ("changed in source") and linked to its successor; a row that disappeared is marked outdated ("missing in source"); a row that comes back is reactivated without being embedded again.
This site needs JavaScript for the full experience. Every page above is reachable without it.