Workflow Reports

Every workflow has its own report, covering how it is performing, the data its runs have collected, and whether the workflow itself is in good shape. Open it from Reports, then pick the workflow.

The report is filtered by date range, so everything below describes the period you have selected rather than all time.

Stats

Four summary cards across the top:

Runs started in the period
In progress, runs still open
Completion rate, the percentage completed
On-time rate, the percentage of completed runs that finished on time

The counts are links. Click one to see the actual runs behind the number rather than guessing which they are.

Below the cards is a fuller table including Median duration and p90 duration. Median tells you the typical run; p90 tells you what the slow tail looks like, and the gap between them is usually more interesting than either on its own. A median of two days with a p90 of three weeks means most runs are fine and a few are stuck somewhere specific.

Further down is the list of people who have been using the workflow.

Collected Data

A spreadsheet of every value the workflow's runs collected in the period, which you can export. This tab appears only if the workflow actually collects data. See How to collect data with your workflows.

Feedback

Feedback submitted by the people running the workflow, split into workflow-level and step-level comments, each linking back to the step it concerns. This tab is only useful once the feedback setting is on for the workflow. See Built-in Workflow Feedback Setting.

Late Steps

Which steps run late, and how badly. For each step you get the late count, the late rate, the median lateness and when it was last late.

This is the most actionable tab in the report. A step that is late in most runs is not a people problem: either its due date is wrong, or the work genuinely takes longer than the process assumes. Both are fixable in the workflow.

Workflow Health

Four checks on the workflow itself rather than on its runs.

Title Length. Flags step titles over 80 characters, and marks those over 100 more seriously. Long titles are hard to scan in a run and get truncated in lists and notifications. Put the detail in the step's content instead. See Embedding links, images, videos, and files in a workflow.
Label Length. Flags data collection labels over 30 characters. Labels sit beside their input, so a long one crowds the field and reads badly on a phone.
Variables. Checks that the variables used in the workflow resolve to something real, and flags any that need attention. This catches the common failure where a step's text refers to a field that was renamed or removed, so the run shows a variable that never fills in. See Using variables in Workflows.
Change Log. Every change made to the workflow, with who made it and when.

What to look at first

For a workflow that feels like it is not working, the order that gets to the answer quickest is: Late Steps to find where it stalls, then Stats to see whether that matches a slow tail in the durations, then Change Log to check whether something changed just before it started going wrong.

Video walkthrough

This video walks through the workflow reporting page and its tabs.