Sign in

When analysis seems stuck

How long a run should take, what the states mean, and when it is worth re-running.

Updated August 19, 2026
2 min read
troubleshooting
analysis

What normal looks like

Analysis runs per review area, and areas complete independently — you will see some areas finish while others are still working. A project with a few dozen documents typically completes in minutes, not hours. A large project with long scanned documents takes longer, because parsing has to finish before research can start.

In Progress means being examined now. It is a working state, not an error.

If nothing has moved for a long time

  1. Check the documents finished parsing. Research cannot start on a document that is still being read.
  2. Re-run the affected area. Extraction results are cached per document by content hash, so re-running does not redo the work already done — it is a cheap thing to try.
  3. Check the status page at /status for a platform-level issue.
  4. Raise a ticket if an area has been In Progress for an unreasonable time. Include the project and the area; we can see the run from our side.

If the result looks thin rather than stuck

A completed run that produced very little usually means the material is thin, not that the run failed. Check the evidence gaps: they tell you which questions went unanswered, which is the actionable version of "the report looks empty". See Evidence gaps and follow-ups.

After changing analysis rules

Changing rules does not rewrite existing drafts, by design — a finding an analyst already reviewed is not altered underneath them. Re-run the areas you want drafted against the new rules, and use full re-analysis if a rule changes what counts as evidence, so cached extraction is not reused.

Next

Was this article helpful?

Votes are read: an article that keeps failing gets rewritten.