If documents are not processed in the way that you would
expect them to be processed by the task route, for example if documents
do not appear in the archive or are not stubbed or deleted, identify
the possible cause by analyzing different logs that are produced during
processing.
About this task
Begin looking for the possible causes of an error in a
top down approach, starting with the less detailed error descriptions
available in the Content Collector dashboard,
followed by the event error logs, and ending with the detailed connector
and the audit log task log files.
Procedure
If the task route is not processing documents as expected,
search for possible reasons in the following way:
- Ensure that only one task route is active and enable logging
for this task route.
- Ensure that your task route includes at least one Audit
Log task at the end of the task route and an error task route that
record information about the status of every item that is processed.
- Begin by checking the Content Collector dashboard for processing
errors.
See Information monitored in the system dashboard for details on how to interpret dashboard
errors.
The dashboard monitors which nodes and which task routes
are active and is where you should begin looking for errors. For example:
| Option |
Description |
|---|
| A node (perhaps even the primary node) is idle. |
If the primary node is idle, nothing can be processed. If
there are errors, check
the event logs for possible reasons. |
| There are task route related errors. |
Check the event logs. |