Skip to main content

​
What a run shows you

A run is one execution of a workflow. Every time the workflow starts, Workflow Machine records a run so you can inspect what happened. Runs are the main way to see whether the workflow behaved as expected in testing and in real usage.

​
Why runs matter

Runs help you answer practical questions:
  • did the workflow start
  • did it finish successfully
  • which step failed
  • what output did a step produce
Without runs, automation becomes guesswork. With runs, you can inspect behavior instead of assuming it.

​
Where runs fit in the workflow lifecycle

The workflow lifecycle usually looks like this:
  1. design the workflow
  2. test it
  3. publish it
  4. monitor the resulting runs
That last step matters just as much as the earlier ones. A workflow is only trustworthy if you can understand how it behaves after launch.

​
Runs view and workflow context

Workflow Machine exposes runs as part of the workflow experience, alongside editing and versions. That makes sense because runs are not separate from workflow building. They are how you validate and improve what you built.

​
Live runs and test runs

In practice, both live and test execution matter.
  • Test runs help you validate setup safely
  • Live runs show how the workflow behaves with real inputs
You should expect to use both. Test runs build confidence, while live runs reveal how the workflow behaves in the real world.

​
A good run review habit

When a workflow is new or recently changed, review the first few runs carefully. That helps you catch:
  • incorrect assumptions about trigger data
  • unexpected branches
  • connection problems
  • outputs that are technically valid but not useful
Run review is one of the fastest ways to improve workflow quality.