> ## Documentation Index
> Fetch the complete documentation index at: https://docs.factagora.com/llms.txt
> Use this file to discover all available pages before exploring further.

# History

> Revisit earlier checks, re-run them, and see whether a verdict has changed

Every check DeepVerify runs is recorded. Open **History** from the icon rail in the side panel.

## What is recorded

One entry per session, whichever surface it came from — a page scan, a selection, a YouTube video, or a Live session. Each entry keeps the claims that were found and every verdict they have received.

Entries show the page or video they came from, the number of claims, how many are still unchecked, and the session's [Trust Score](/guides/deepverify/understanding-results#trust-score).

Selections made on a page you already scanned join that page's existing entry rather than creating a new one, so checking the same article five times leaves one row, not five.

<Note>
  Where history is kept, and whether it follows you between devices, depends on your plan. See [Pricing](/guides/deepverify/overview#pricing).
</Note>

## Re-running a check

Any claim in History can be checked again. This is the point of keeping the record: a claim that was unverifiable last month may be settled now, and a claim that looked true may not survive later reporting.

Re-running **adds** a verdict rather than replacing the previous one. The card shows the latest verdict, and the earlier ones stay underneath — so you can see that something changed, and when.

For the same reason, re-checking a YouTube video does not overwrite the earlier entry. Both results are kept.

<Note>
  If a re-check fails — no connection, service unavailable — nothing is recorded. A failure never shows up as a verdict that changed.
</Note>

## Next

<CardGroup cols={2}>
  <Card title="Understanding results" icon="circle-check" href="/guides/deepverify/understanding-results">
    What each verdict and score means
  </Card>

  <Card title="Settings" icon="gear" href="/guides/deepverify/settings">
    Every setting in one place
  </Card>
</CardGroup>