Skip to main content

​
Get familiar with the Runs tab

For each run, the list shows:
  • The name of the schedule that triggered the run The current number of fully passing attempts over the total attempts made. — The number of flows in the run that still require investigation (if applicable). — The number of open bug reports linked to flows in the run (if applicable). — The number of open maintenance reports linked to flows in the run (if applicable).
  • Total wall clock time of the run, including all attempts.

​
How to sort and filter run histories

  • The default view on the Runs tab displays past runs, sorted by date in descending order.
  • You can filter the list by clicking the icon.
  • Created date lets you filter runs by 1 week ago, 1 month ago, or 1 year ago.
  • Trigger lets you filter runs by schedule frequency: Hourly or Weekly.

​
How to identify failed runs that need attention

1
Go to the Runs tab. The icon next to the environment name indicates the status of flows from previous runs.
Environment statusMeaning
Red – FailedHigh severity bug reported
Yellow – Needs investigationFailed flow

or

Medium or low priority bug reported
Green – ReadyAll flows passing
2
Select the environment you are investigating. Runs are sorted into three categories:
  • Completed: All flows in the run have passed or been marked Do Not Investigate.
  • Investigating: Flows in the run failed, but have not been marked Do Not Investigate.
  • Canceled. The run was cancelled mid-execution by a subsequent run matching the same branch and environment.
Last modified on March 2, 2026