Source: https://seerepo.com/docs/scan-queued-or-failed
Markdown source: https://seerepo.com/docs/scan-queued-or-failed.md
Description: What each scan message means, what you can do while you wait, and how big a repo can be.

# My map is queued, in line, or the scan failed

While SeeRepo reads your repo, a notice on your project says where it is. On your panel, its card says it in a few words: "Drawing its map…" while it reads, and "Its last read failed" if it failed. A failed read keeps its place on the panel: SeeRepo's team is already warned, and there's nothing for you to fix.

## "Your first scan is queued."

Your repo is waiting for the reader. It usually starts within moments. Then you see "Scanning your repo…" and the stages, from "Getting your code from GitHub…" to "Your map is ready. Adding the details…".

## "Your repo is queued to be read again."

A repo that already has a map is read again from the start, for example after you change its timezone or ask for another read. Your map stays on screen while it waits, and catches up when the read ends.

## "Many repos are being read today: yours is in line."

Free repos share a daily budget of first loads. When it runs out, your repo waits its turn: it tries again every few minutes, oldest first. You don't have to keep the page open: "You can close this page: we'll write to you@example.com when your film is ready." You'll get an email, **"Your your-repo film is ready"**, unless you watched it happen or turned email notifications off in your account settings (then the page says your film will be waiting there). Someone you invited who opens the repo meanwhile reads that it's in line too.

## "This repo has no changes yet. SeeRepo reads it at your first push."

Your repo on GitHub is empty: there's nothing to read yet. Push your first commit to its default branch and SeeRepo reads it then. With the project open, you watch its first load right there.

## "The scan failed. We'll look into it."

If your first load fails before your map is ready, the film stops there. While another try is on its way, the page says "That read didn't finish. SeeRepo tries again by itself in a minute, and the film starts over." This notice shows once the last try fails, for you and for anyone you invited who's watching. A scan that fails is tried again, up to three tries in all. A repo that's too big isn't tried again, because another try would end the same way: one over 5 GB on GitHub (its whole history counts), or one that takes too long or needs too much memory to read. When the last try fails, SeeRepo's team gets an alert about your repo, so it's seen without you writing in.

What you can do:

- **Read it again.** The notice has a **Read it again** button for the repo's owner. It asks for one more read, once: the button doesn't queue a second one while one waits. It isn't there on a repo GitHub disconnected, a frozen one (its plan decides) or a free repo already drawn (it's read once). If a push arrives after the failure, the notice follows that read instead. It won't help a repo that's too big. You can also close the notice with its ✕.
- **Wait for the next push.** Each map is read again with every push to its branch.
- **Tell us what you see** on the [ideas board](/feedback), with the repo's name.

## Good to know

- A free repo is read once: its pushes aren't read until it has a plan.
- The first map arrives in under a minute for a medium repo, and in a few minutes for a very big one; the details keep arriving after.
- A file over 5 MB is seen but not opened: its lines aren't counted.