Troubleshoot Workflows with Run Log
This Help Article Appears in the Following Learning Tracks
The Run Log can be found in the Designer, to the right of the workflow. It is a useful tool to help you troubleshoot existing workflows and build new ones.
In the Run Log you will find all the Runs of a workflow, each time your workflow was triggered. It gives you access to run statuses, run times, and data contained in the workflow.
You can also quickly copy data values or data references from here.
The panel shows a list of each run, documenting the run's current status and the time since the workflow started executing. You can click on a specific run to understand which steps were executed within it.
Use the filter at the top left to see only Stopped, Waiting, In Progress, or Completed runs.
Reference data from a Run Log
You can use the Run Log to update the referenced data in a module:
- Trigger the workflow to run as far as it can.
- Then, open the run in the Run Log and expand the step where the data was collected.
- Next to the data object, expand the dropdown from the three dots and copy the reference to the data or the actual value.
Identify the cause for a stopped run
If a run was stopped because of an error, when you click on the run the failed module step is automatically expanded to display the error that occurred.
For example, the workflow shown at the start of this guide is triggered by new rows added to a sheet in Smartsheet. The error in the image above tells us that the Get Row module couldn't execute since the Row ID field hasn't been set.
To solve this:
- Expand the Trigger step and find the rowID. This is the new row that was added to the sheet.
- Next to it choose Copy Data Reference in the dropdown.
- You can now go to the setup panel of the Get Row module and paste in the reference to the Row ID.