Processing logs and support details

The processing log is the fastest way to tell whether an issue is document-specific or caused by setup.

How to Read the Log

• Start with the first Error line, not the last one.
• Look at the process stage where the failure begins.
• Use the message to decide whether the problem is upload, connection, analyzer sync, matching, review, or document creation.

If the log shows a connection or setup problem, fix that first and then decide whether a retry makes sense.

What to Collect Before Asking for Help

Before asking an admin or support person for help, collect:

• the document Entry No.
• the Analyzer Code
• the document Status
• the first Error message from the Processing Log
• whether a created document number already exists

That is usually enough for someone to tell whether you should retry, review, or fix setup first.

Current Log Limits

The Processing Log page currently displays only Entry No., Created Date, Log Type, Process Stage, and Message.

The log table defines extra fields such as HTTP status, stack trace, detailed message, duration, and additional data, but the current logging flow does not consistently populate or surface them to users.

The log table includes stages for Field Mapping and Posting, but the current processing flow does not write user-facing log entries for those stages.

A Debug log type exists in the table, but there are no current code paths writing debug entries.

Because of those gaps, the guidance in this section focuses on what users can actually see and do today: queue status, review flow, retry flow, created-document checks, and the basic processing log messages.