Run Log Analyzer (Run History report)


The Run History report includes an AI analysis option for administrators. It reads the log of a run - an Automation run, or the activity of a user whose Workflow Monitor is on - and explains in plain language what the run did, what went wrong or was slow, the likely cause, and what to change. It only reads the log; nothing in DocMgt is changed.


There are two ways to run it. In an open log, the Analyze button analyzes that run. The Analyze a Log button at the top of the report analyzes a log that is not in the list, for example one that was downloaded earlier or sent to you: choose a .log or .txt file, or paste the text. Logs up to 2,000,000 characters can be analyzed.


Both buttons appear only for users with both administrator and reporting rights, the same rights Run History itself needs. They also require AI to be licensed with an available AI usage allowance.


For an Automation run, the assistant also reads the Action Set the Automation runs, so it can tie each error to the action that caused it and point you at the action to change. It reads the Action Set as it is set up now; if the Action Set has changed since the run, the analysis may say so. Workflow Monitor runs, including Add-In clicks, are analyzed from the log alone.


A very long log is not read in full. The assistant reads the start, the end and the lines around every error and warning, together with exact counts of everything in the log, and the analysis says when this happened.


The result starts with a short summary: whether the run did its job, the main problem, and what to do first. The findings follow, grouped as Errors, Warnings and Notes. Each finding says what happened, the likely cause and what you can do about it, and lists the log lines it is about. In an open log, click a line number to scroll the log to that line. Copy copies the analysis to the clipboard and Download saves it as a text file.


A run that did its work with no errors or warnings is reported as clean. The assistant does not invent concerns to fill the list.


The suggested fixes are limited to things you can do inside DocMgt for your own tenant - for example correcting an action in the Action Set, the Automation, a workflow step, a Record Type or field setting, a template, or a security right; fixing the record or document involved; re-running the Automation; or, when something genuinely needs system access, contacting DocMgt support with the run's date and time and the message. The assistant never reports on the infrastructure DocMgt runs on, because that is not something you administer or can act on.


The analysis is not saved with the run. Past analyses are listed under My AI Activity in your user menu, so you can re-open one later without running it again. Each analysis counts against the same AI usage allowance used by features such as the Document Summarizer; if the allowance has been reached the assistant reports that instead of running.


To use it: open Reports, run Run History, click the View Log icon on a run, and click Analyze. To analyze a log you already have, click Analyze a Log instead.


NOTE ON (AI): Analyzing a log with AI consumes tokens from the End User pool and may incur extra fees. Check with your sales rep for more information. Please verify all results, as AI can make mistakes.