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

# Connecting over years of history

> A project with years of stored errors behind it reads the same, and takes the same time, as one connected yesterday.

Most products of this kind quietly assume you are starting from nothing. This
one assumes the opposite: you are pointing us at a project that has been
collecting errors for years, and none of that is going to be thrown away to make
us comfortable.

That assumption has a cost we are the ones who pay. This page says where it
lands and what you should expect to see.

## What grows, and what does not

Your stored history grows for as long as you are with us. Two things could grow
with it, and only one of them does.

| As your history grows            | What happens                                         |
| -------------------------------- | ---------------------------------------------------- |
| How much we hold for you         | Grows. That is the point of holding it.              |
| How long the Findings page takes | Flat. It does not move with the size of the history. |

The Findings page shows the most recent findings, and how long it takes to draw
is set by how many findings are on it — not by how many errors sit behind them.
A project with a decade of errors and a project connected this morning draw the
same page in the same time, given the same number of findings on it.

## Why that is not automatic

The Findings page asks one question that could have gone the other way.

A finding [raised during your first fortnight and released at the end of
it](/guides/your-first-fortnight) tells you whether the error behind it has been
seen again since the day it was raised. Answering that means finding the most
recent report of that error — and "most recent" is a question you can answer
either by reading everything and picking the latest, or by going straight to the
latest.

Reading everything is the version that gets slower the longer you have been with
us, on a page you open every day, forever. So we go straight to it. The answer
is identical; what changes is that the work does not grow with the pile it is
looking into.

<Note>
  It also means the page asks that question once for the whole page rather than once per finding, so
  a full page of released findings costs one question and not fifty.
</Note>

## What you should expect

* A Findings page that does not get slower as your history gets longer.
* The same readings either way. A finding that has not been seen again still
  says so; one that has still names the most recent time it was reported to us.
* No archiving, no retention window, and nothing you have to prune to keep the
  product quick. Trimming your history to make our page fast would be us
  charging you for our own problem.

If the Findings page ever does feel slower after a long relationship with us,
that is a defect and not a limit you have run into. Tell us, and say roughly how
long you have been connected.