Operations

Work out what happened to an interrupted scan

A scan can be interrupted by a restart, a deploy, a stop button or the machine running out of room. The product is built so that none of those throw away the work that was already done.

What to do

Open Scans. An interrupted run says interrupted rather than finished, and never claims a clean result.
Look at what it kept. Repositories the scan had already finished are ingested and their findings are on the list.
Repositories it never reached are left exactly as they were. Nothing in them is counted as fixed, because nothing looked at them.
Read the log excerpt on the run. If the scan failed rather than being stopped, the reason is stored with it rather than only in a container log that has since rotated.
Start another scan. It will cover the whole scope again, and the findings that were already ingested are matched rather than duplicated.

Worth knowing

Check the Scans page before recreating the container. A scan interrupted ninety minutes in is ninety minutes of cloning and reading that has to happen again.