Run History lists the runs of your Automations and the workflow activity of users whose Workflow Monitor is on: when each run happened, how long it took, how it ended, and the first error it hit. You can open a run's full log and download it.


Run History is available on Enterprise and higher. You need both Administrator and Reporting rights to see it. If either is missing, Run History does not appear in the list of reports.


What appears in Run History

Automations - every time an Automation runs on its schedule, it adds a run.

Workflow Monitor - while a user's Workflow Monitor is on, each thing that user does that runs workflow (for example clicking a workflow button or routing a record) adds a run, with its full log. Nothing is added for that user once the monitor is stopped or has turned itself off after 24 hours. Requests that did not run any workflow add nothing.


Opening Run History

Open Reports and choose Run History in the Workflow group.

You can also start from an Automation. Open the Record Type, go to the Automation section, and click the Run History icon on the Automation's row. Run History opens in a new tab, showing only that Automation's runs, so nothing you are editing on the Record Type is lost.

To see a monitored user's runs, open the user in Users, go to the Workflow Monitor section, and click Run History. It opens in a new tab, showing only that user's runs.


Finding runs

Source shows only Automation runs or only Workflow Monitor runs.

Status shows only the runs that ended a certain way, for example only Failed runs.

Run Date limits the runs by the day they started. It starts out set to the last 7 days.

When you are looking at a single Automation's or user's runs, Source shows its name instead. Click the clear button next to it to see every run again.

Results per Page sets how many runs are listed on each page.


Click Run Report to show the runs. Download saves the runs that match as a CSV file.


Reading the results

Started is when the run began. Hold the pointer over it to see when it ended.

Duration is how long the run took.

Source is what ran. For an Automation it is the Automation's name, with its Record Type next to it. For the Workflow Monitor it is the user's name followed by what the user did, for example Running Add-In 'Approve Invoice', Processing Workflow - 'Approve' on 'Manager Review', Routing Record 1234 into Workflow, Opening Work Item at 'Manager Review', Reassigning Work Item at 'Manager Review' or Running E-form Actions. When one click did several of these, the run is named after the main one, such as the button that was clicked. Click the name to show only that Automation's or that user's runs.

Status is how the run ended:

  • Running - the run has not finished yet.
  • Succeeded - the run finished with no errors or warnings.
  • Warnings - the run finished, but something along the way reported a warning.
  • Failed - the run stopped on an error, or one of its actions reported an error.
  • Cancelled - the run was stopped before it finished.
  • Abandoned - the run stopped reporting progress for two hours, most often because the server processing it restarted part way through. Check the next run of the same Automation.

For Workflow Monitor runs, Failed means an action reported an error. An error that stopped the user's request before any action ran, such as a workflow button that was not allowed, is shown to the user but does not mark the run as failed.

Actions shows the number of actions the run performed, then the number of records those actions worked on.

Errors shows the number of errors, then the number of warnings.

First Error is the first error the run reported. It is usually the cause of the failure.


Viewing and downloading a log

When a run kept its log, its row has a View Log icon. Click it to open the log. Each line starts with its line number. Errors are shown in red and warnings are highlighted. The times in the log are UTC.


Click Download to save the log as a text file, for example to send it to support.


An Automation run keeps its log when it fails. To keep the log of every run, including the ones that succeed, open the Automation and turn on its Run History switch so that it reads Keep the log of ALL runs.


Workflow Monitor runs always keep their log.




Analyzing a log with AI

AI can read a log and tell you what went wrong and what to change. It only reads the log; nothing is changed. The Analyze and Analyze a Log buttons appear only when AI is available on your system.


Analyze - in an open log, click Analyze. For an Automation run, AI also reads the Action Set the Automation runs, so it can point you at the action to change. It reads the Action Set as it is set up now, so if the Action Set has changed since the run, the analysis may say so.


Analyze a Log - click Analyze a Log at the top of Run History to analyze 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, then click Analyze. Logs up to 2,000,000 characters can be analyzed.


Reading the analysis

The analysis starts with a short summary: whether the run did its job, the main problem, and what to do first. The line under the title gives the number of lines, errors and warnings in the log. For a very long log it also says that AI read the start, the end and the lines around the errors and warnings.


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 in a finding to scroll the log to that line.


The analysis is not saved with the run. Copy puts it on the clipboard and Download saves it as a text file.


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.


How long runs are kept

Runs are kept for 30 days and then removed. For each Automation, the logs of the newest 100 runs are kept. Older runs stay in the list but no longer have a log to view. Workflow Monitor runs keep their logs for the full 30 days.

For on-premise installations, the number of days can be changed with the Run History setting in the System Clean Up section of Main Options. A value of 0 keeps the standard 30 days.