When you view a flow, the Run history tab provides an overview of your flow's status, duration, and start and completion times, among other things.
You don’t need to scroll through the entire history of your flow to pinpoint a date and time. You can choose from six predetermined ranges or create a custom range:
-
Today
-
Yesterday
-
Last 24 hours
-
Last 7 days
-
Last 15 days
-
Last 30 days
-
Custom
Using ranges helps you review flows that run once a day or less; for example, every other day, weekly, bi-weekly, or monthly flows. On the other hand, if you’re looking for a specific date(s) or time(s) you should try the Custom range.
Custom ranges are helpful for reviewing large data sets (over 30 days) or more specific dates (Monday to Wednesday). You can also filter by a specific time or range of times, like 12:00 a.m. to 1:00 p.m. These custom ranges can be combined to create unique date and time searches such as 10/20 to 10/23 from 12 a.m. to 1 p.m.
You can filter the run history based on the status. Each status has a distinct color, and this visual cue enables you to get a high-level understanding of flow runs at a glance. For example, if you see a lot of yellow in the Status column, this means that a lot of your flows were canceled and you might want to filter based on the Canceled status to view all the canceled runs and investigate further. Filtering flow runs can enable you to examine and analyze details and find patterns or detect issues. You can select any of the following flow statuses to filter and view your runs:
If you select the Canceled status to filter, you can additionally select Canceled by and view flow runs canceled by any user or the system.
Now, you can easily view who canceled a flow run by clicking the info icon next to the Canceled status.
You can check or uncheck the Hide empty runs or Hide retry runs to exclude all jobs without records (i.e. Success, Ignored, and Errors columns are all 0) or retry runs.
You can now filter to view the runs that contain errors. This option helps identify and troubleshoot failed runs without manually sifting through successful runs.
You can now see retry jobs directly in the Run history tab to track how a record moved through each step, including any retries.
Retry jobs appear alongside flow jobs and clearly indicate who started them. If you triggered the retry from the UI, your name is shown; otherwise, system is shown in the triggered by column. You can also filter manual and system retries and view both running and completed jobs.
When a retry occurs, all downstream steps appear in the Run history by default.
You can cancel any running job (flow or retry) from the Run history.
Note
Triggered by is shown only for retry jobs.