Unanswered

Duration in flow run history

(1) Share

Report

Posted on by vamshik153

Hi Everyone ,

I want to exact meaning of Duration in Power Automate flow Run History . Is it the time taken to hit the action or complete the action ?

For example if i create the flow to refresh Power BI Dataset for every 15 minutes . in the job run history i can see time in ms for success jobs . So is this time in ms is the time taken to hit the action (triggering the refresh) or time taken to complete the action(Complete the refresh ).

Please help me on this

Categories:

General topics

I have the same question (1)

All responses (2)

Answers (0)

Sort by

poweractivate 11,078 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

@vamshik153

I believe that duration would be the time taken to complete each and every step in the Flow. So I believe the answer would be "both" and even more than that, "all" parts of that Flow run.

In other words, it would be the time taken for not only the trigger block to complete, it would be the time taken for each and every other action block in the Flow to complete. So if the trigger is doing something, it counts that time (I believe even that block technically might be taking some time, though for most triggers it is usually a very small amount of time, so it might show as 0s when opened up and inspected individually), and for each and every action, that time for each action is taken and combined, and you get the total time you see for the Flow in that column in Run History.

To see individual times of each action, you can open the run history and see visual representation of how much time it took for each block - including the trigger block itself, as well as each individual action block.

Essentially, the time you see in that specific column "Duration" in Power Automate is the sum of the total time taken for all parts of the Flow run - the Flow trigger and the Flow actions as well. By the way, I don't see it in milliseconds, but actually in hh:mm:ss (hours:minutes:seconds) in that column, example:

In above example, each of these runs took approximately 3 seconds in my case, (and not 3 milliseconds).

Check if it helps.

Was this reply helpful? Yes No
binki 4 on at

Like (0)

Report
Copy link

Link copied!

Hello,

When I look at the flow run history, I can see runtimes in ms (milliseconds) unlike what poweractivate shared in his post.

I found that the runtime in milliseconds accounts for the total runtime of the entire flow except for the runtime shown on the trigger. For example, I have a flow run which had a duration of 814ms and, in the details, shows that the trigger took 2s and my one action (a condition) took 0.5s.

Note that 814ms is insufficient to account for all of 2s + 0.5s (2.5s). From this, my only conclusion is that the duration recorded starts sometime after the trigger starts processing and ends sometime after the last action execution ends (though I have no way of proving that other than noting that the flow runtimes I have seen are never less than the total runtimes shown for all of the actions).

One possibility here is that the total flow duration includes some of the orchestration/execution engine time—i.e., the time that the flow execution engine spends deciding to run the next step—in addition to the actual action execution times.

I do find it interesting and surprising that most of the trigger execution time is excluded from the flow’s total runtime.

I find it frustrating that the flow run history shows milliseconds (which is very helpful) while the actual breakdown of a specific flow run only shows tenths of a second. When my action’s execution time is lower than 0.05s, it unhelpfully displays this as 0s. I presume that the thing to remember is that the action runtimes will be shown to the nearest tenth of a second even though the GUI does not display significant digits. I.e, you can and should treat “0s” as “0.0s” which could be any value from 0.000s (0ms) through 0.049s (49ms). But that doesn’t help if you are trying to identify which actions are slower than others—enough 49ms actions will add up compared to 3ms actions.

Was this reply helpful? Yes No