Run Detail

Run detail is the record of one run. It shows the graph as it was when the run started, the status of every node, the items each node received and produced, and the events of the run in order, and it opens from a run's row in Run Logs. Use it to find where a run stopped, what a node received, how long each node took, and to cancel a run or rerun it from a node.

The Run Graph

Run detail shows the same graph as the Builder, from the Revision the run started with, so an edit made after the run started does not change what run detail shows. Each node shows its status, and each connection shows how many items passed along it, so a Filter node that received 40 items and passed on 12 shows 12 on the connection after it. A node that received no items shows the status Skipped, which is the expected result of an If, Switch, or Filter node routing every item elsewhere and not an error.

The run's status and Revision are shown with the graph, along with Cancel Run while the run is Running and Download Journal once it has finished.

A Node's Record

Selecting a node opens its record, in five tabs.

Overview shows the node's Status, its Execution Stage, which names how far the node has progressed through planning, validation, and execution, when it started and finished and how long it took, whether it reused the output of an earlier run, its counts of Successful Operations and Failed Operations, and its Error Types. Reused Upstream Output is Yes on a node whose output a retry or a rerun reused from the original run rather than produced again.

Inputs lists the items the node received, with each item's type and value, and Outputs lists the items it produced, grouped by the output they were routed to. For a file item, the value is the file's path.

Errors lists the errors recorded for the node's failed items, and Journal lists the node's events in order, from the node starting to the node finishing, with the items produced and the items failed in between. Each event opens to its details, including the number of items in and out, the operation counts, and the duration, and the list can be filtered to items or errors.

Canceling a Run

Cancel Run stops a run that is Running. Nodes that have not started are canceled, the node in progress completes its operations, and the run finishes with the status Canceled. A run can also be canceled through the Files.com API.

Rerun from Node

Rerun from Node, on a node of a finished run, starts a new run that resumes at that node. The nodes before it are not run again and their outputs from the original run are reused, which each reused node's Overview records as Reused Upstream Output, and the selected node and every node after it run again. Choosing the trigger node reruns the whole run, and the new run is linked to the original in Run Logs as Rerun of Run, with the Node ID it resumed at.

Use Rerun from Node after fixing what made a node fail, for example after approving a command on an Agent or restoring a Remote Server's credentials, to complete the run without repeating the nodes that succeeded. Retry Handling resumes a failed run at its failed node and reuses the earlier nodes' outputs, without anyone starting it.