Recurring checks

Use a simple review cadence so problems are caught before they block document flow.

Daily or Frequent Checks

Check the Document Queue.

• Look for documents stuck in Pending.
• Look for documents stuck in Processing.
• Review anything in Error.
• Review anything in Review Required.
• Confirm completed items are continuing to appear.

If documents are not moving, first confirm:

• auto processing is still enabled in setup
• the processing schedule still exists and is not on hold
• at least one analyzer is active

If a document failed, use the processing log for that document before changing settings broadly. A retry is safer than rebuilding configuration.

Weekly Checks

Check the Analyzers list and each analyzer card as needed.

• Confirm the right analyzers are still active.
• Review processed document counts and average confidence.
• Watch for analyzers with repeated review needs or repeated failures.
• Confirm any analyzer used for automatic document creation still has the right threshold and review expectations.

If you use automatic matching, also review the matching setup regularly.

• Confirm tolerances are still appropriate.
• Confirm blocking behavior still matches policy.
• Confirm auto-approval settings are still acceptable for your control environment.

Monthly or Policy Checks

Review setup values that affect risk and storage.

• Retain Documents Days
• Delete After Processing
• Enable Auto Processing
• Auto Process Interval

If you use a connected file library, also confirm:

• the connection still tests successfully
• the selected site, library, and root folder are still correct
• the scan schedule still exists and is not on hold
• files are moving through the expected folders

If the Queue Stops Moving

Use this order before you make broader changes:

1. Check whether auto processing is enabled.
2. Check whether the processing schedule is on hold.
3. Confirm at least one analyzer is active.
4. Open the processing log for recent failures.
5. Retry only after the likely cause is understood.

For detailed issue diagnosis, continue to Troubleshooting.