Run Logs
Run Logs is the list of an Automation's runs, one row per run. Each row opens the run's run detail. Use Run Logs to check whether last night's run succeeded, which runs failed and whether they were retried, and which Revision of the Automation a run used. The site-wide Automations Logs is compared in Run Logs vs. Automations Logs below.
What a Run Record Shows
Each row shows the run's ID, which opens run detail, the Revision of the Automation it ran, its Retry Linkage, its Status, its counts of Successful Operations and Failed Operations, its Created At and Completed At times, and a Download Journal action. An operation is one file operation performed by a node, for example one copy, so a run that copied 40 files to two destinations records 80 successful operations.
Run Statuses
| Status | Meaning |
|---|---|
| Queued | The run is waiting to start. |
| Running | Nodes are being processed. |
| Success | Every node that ran succeeded. |
| Partial Failure | One or more items failed, and every failure was handled by an Error Handling rule set to Continue. |
| Failure | A failure was propagated or matched no Error Handling rule. |
| Skipped | The trigger produced no items, for example when no file matched the folder path and pattern, so no node ran. |
| Canceled | The run was canceled from run detail or through the API. |
Retry Linkage
Retry Linkage shows how a run is related to another run. A run that is neither a retry nor a rerun shows Not set. When Retry Handling starts a new run after a failure, the original run shows Retried In with the new run's ID, and the new run shows Original Run with the original's ID. A run started with Rerun from Node shows Rerun of Run with the ID of the run it reran and From node with the Node ID it resumed at.
The Run Journal
Every run has a journal, a file in which each line is one event of the run. A node starting, the items it produced, the items that failed, and the node finishing are recorded as events. The same events are shown per node on the Journal tab of run detail, and Download Journal saves the whole run's journal as one file for a support case or your own analysis.
Notifications About Runs
To be notified when a run finishes, create an Event Channel subscription for the Automation event types: Success, Failure, Partial Failure, Skipped, Failure Will Retry, and Partial Failure Will Retry. The two Will Retry types are recorded when a run failed and Retry Handling will start a new run. Site Administrators can also receive Automation failure emails, which cover failures and partial failures after every retry has been used and do not cover failures that will be retried.
Run Logs vs. Automations Logs
Run Logs lists the runs of one Automation. The site-wide Automations Logs lists the operations of every Automation on the site, one record per file operation, retained for 180 days, and each record of a node's operation includes the node's ID and type and, for a failure, the error type. Use Run Logs to follow one Automation and open its runs. Use Automations Logs to search operations across Automations, for example every failed operation on the site in the last week.