# Answers that may be out of date: when a document changes after it was cited

When a document an answer quoted changes, GPTree checks that answer again and labels it May be out of date, with a sentence saying exactly what happened to the passage it quoted. The answer itself is never changed.

An answer that cites your documents points at the exact passage it quoted, in the version it quoted. Documents move on: a policy gets a new version, a handbook is replaced, a file is deleted. GPTree notices, goes back to every answer that quoted the document, and checks what happened to the passage each one rests on.

The answer is never edited. GPTree reports what changed under it, and you decide what to do.

## What the label says

An answer whose source changed is labelled **May be out of date**, followed by one sentence that says only what the check found:

- **The passage it quoted changed on 4 November.** The words it quoted are not there as they were.
- **The passage it quoted could not be found in the version of 4 November.** The passage may have been reworded or moved rather than deleted; GPTree only knows it could not find it.
- **The document it quoted was deleted on 4 November.**
- **The document was updated on 4 November, and the passage it quoted is still there.** Something else in the document changed. The quote itself is intact, word for word.
- **The document was updated on 4 November, and the passage it quoted could not be compared.** The passage was too short to compare reliably, so GPTree does not guess.

The date is the day the version that applies now was added, or the day the document was deleted. "Updated" means a newer version, or a newer document confirmed as replacing it. It does not mean the date a policy takes effect.

None of these says the answer was mistaken. A changed passage is a reason to look again, not a verdict.

## Where you see it

- **On the Knowledge page.** Open a document and look at What it has affected. Each conversation and crew run that cited it carries the label for how this document's change affects it.
- **On the message itself.** A chat reply whose sources changed shows a small May be out of date label. It reflects every document the reply cited.
- **In the tidy-up list** on the Knowledge page, grouped by document.
- **On Knowledge health**, as the Possibly stale answers tile, for workspace owners and admins.
- **In the Knowledge API**, through `GET /impact` and the `answer.impacted` webhook for your own API answers.

## Checking for changes

Checks run in the background within minutes of a change. Until an answer has been checked, the stale answers list and the answer's details read **Checking for changes**, never as if nothing changed. In a conversation, a reply carries a label only once a check finds something, so an unchecked reply shows no label there yet. If an answer already had a label, it keeps it while the new check runs. If checks of an answer keep failing, it says **Last check failed** with the time of its last successful check, so a stale result is never passed off as a current one.

## What changed in its sources

Click a label to open the detail. For each document the answer cited it shows the version it quoted, the version that applies now, the sentence above, when it was last checked, and whether a check is waiting or failed. When you can open both documents, the passage it quoted and the closest passage in the current version sit side by side. A document you cannot open, such as a colleague's private file behind a conversation they shared with you, is shown only as **A document you cannot open**: the detail still says what happened to it, but not its title, its versions or its dates.

For a chat reply there is also **Re-ask in a branch**: it asks the same question again in a new branch, against today's documents, and opens Compare on the original answer and the new one. It is charged like any message, and the original stays exactly as it was.

## Who sees what

You see the label only on answers you can already open. A conversation shows its labels to anyone it is shared with. A crew run's label is shown to the crew's owner only: a workspace member who can open a run does not see its label. Nobody is told how many answers they cannot see.

## Two limits for chat

- **An edited reply can lose a source but never gain one.** If you edit a reply and delete a citation, that document stops counting for it. A citation typed in by hand is not tracked.
- **A reply copied in by a merge is not tracked.** A merge that writes a new message records no citations for it, so it never gets a label.

Chat replies and crew runs get labels. Retraction notices (`answer.unsound` in the Knowledge API) stay for Knowledge API answers only.
