Nebula AI Case Explorer™ | Project Status, Processing, and Exceptions
Analyzing a large document set takes time, and not every document makes it through cleanly. This article covers what you'll see while that happens and what it means.
What you'll see while processing runs
Different parts of the product become available as their underlying processing finishes — you don't have to wait for everything to be ready before you can start looking at results. Expect messages like "this section will be available once analysis completes" on pages that aren't ready yet, rather than an error.
On the Case Overview specifically, a banner tells you the current state:
- Processing — analysis is still running; the page fills in as results become available.
- Success — analysis completed with no exceptions; all data is available.
- Partial — analysis completed, but with some exceptions. A link opens the status report for details.
- Failed — admins get a link to the status report to rerun; other users are told to contact their administrator.
The status report
The Status Report (available from a project's three-dot menu, or from the exceptions link on Case Overview) shows project details — name, document count, status, date started, last update — and, if the ingestion pipeline failed, a Rerun AI Analysis option for admins.
What counts as an exception
Not every document is fully processed, and that's expected rather than a sign something is broken:
- Some document types are excluded from AI processing by design — a full list is available on request from your KLDiscovery team.
- Documents whose extracted text exceeds a size limit (300KB) are flagged in the exceptions report rather than silently dropped, and rather than causing the whole run to fail.
- A small number of documents may be excluded because their content trips an underlying content-safety filter rather than a size limit — these are also captured as exceptions, not silently skipped.
- Very short documents may not receive a full AI-generated summary.
By design, an excluded or failed document does not show up in Document Explorer at all — it's not that it appears with blank fields. The only place to see what was excluded and why is the downloadable exceptions report, not the document list itself.
If something fails outright
A generic failure message means a temporary system error interrupted the run. Try again first. If it persists, contact your KLDiscovery team — see Getting Help and Giving Feedback.
The product is designed so failures show up as a plain description of what happened rather than a raw technical error, and that coverage is still being filled in during the pilot — if you ever do see a raw error code or an unfamiliar technical message, treat it as worth reporting rather than something you did wrong.
Related articles