Full analysis runs every selected analysis in one background task. You can keep working while it runs, and on a large org it can run for hours — so it is built to be interrupted, resumed and watched.
Start it from a graph with Refresh → Full analysis, or from a folder to run several orgs in one batch.
The launcher reads what your current version actually has and offers to tick only what is missing or incomplete. A run that finished without related-object volumes should be answered by re-running one analysis, not nineteen.
Each analysis with a time window has its own period, so you can refresh a two-week DML window without touching a six-month audit trail.
They stop the run equally quickly. What they do with the work already done is opposite.
Pause stops after the current analysis and keeps everything computed so far. Nothing is rolled back. No version is committed yet, and the run can be picked up later.
Cancel stops and rolls back. Every analysis from this run is discarded and the previous results are restored, exactly as though the run had never started.
Both wait for the analysis in progress to finish, which can take a few minutes — the banner says which one you asked for while it waits.
A paused run leaves a Resume button on the banner. It re-runs only what is left.
Some analyses always re-run: the backbone pass and the four that depend on it share the work it does, so they cannot be skipped in isolation. The launcher tells you how many analyses a resume would genuinely skip, rather than implying it can skip all of them.
If you closed the app instead of pausing, the work still survives — the next time you open the launcher it offers to keep it.
The banner shows the current analysis and how long it has been running. Some steps report progress rarely, and on a long one a clock is the only honest way to tell "still working" from "stuck".
A full analysis commits its version at the very end, so for most of the run the KPI, dashboard and licensing screens are still showing pre-run numbers. If you want to see what has landed so far, open the version menu and choose Refresh in progress. The screens fill in as each analysis completes, and a bar across the top makes it clear that nothing you are looking at is committed yet. One click returns you to the committed version.
The Apex, Flows and DML views update themselves during a run as soon as their own analyses finish, without any of this.
From a folder, Full analysis runs the same selection across every org you tick. You choose how many run at the same time — two is a sensible default. Salesforce limits are per org, so different orgs do not compete with each other, but each analysis starts processes on your own machine.