What to Do When Deep Context Scan Is Stuck at 0% or Progressing Slowly

If your deep context scan appears to be stuck at 0% or is progressing very slowly, this is typically due to high system load rather than an issue with your specific processing job.

Why this happens

Deep context scans can take longer than usual when:

• There is high processing load on the system

• Your document set is particularly large or complex

• Multiple users are running processing jobs simultaneously

What to do

In most cases, no action is required on your part:

1. Wait it out - The processing will continue and complete automatically, even if the progress indicator appears stuck

2. Don't restart the job - Your chronology is still processing in the background

3. Be patient with large document sets - Complex or large document collections naturally take more time to process

The system will typically begin processing normally within 20-30 minutes during periods of high load. You should see the progress indicator start moving and the job will proceed through the "extracting facts" phase and complete successfully.

When to contact support

If your deep context scan is longer than an hour with no progress, or if you receive any error message, please contact our support team for assistance. We'll be able to check for updates, and help resolve the error as quick as possible.