Unable to see flow errors for failed flows in the history log

(2) Share

Report

Posted on by SPCloudguy

111

Hi,

I'm still having problems when flows fail the history log doesn't show the complete list of actions so I'm unable to see where the flow is failing for an un-attended flow.

Along with viewing the history logs through the browser, I've tried using the Power BI report from the COE but that still doesn't show all actions.

Has anyone else had issues viewing errors and found how to resolve it?

Categories:

Power Automate Desktop

I have the same question (0)

All responses (4)

Answers (0)

fraenK 2,125 on at

Like (0)

Report

I'm investigating the same issue right now.

So far, I could only find out, that the run history seems to be limited to 9999 entries/actions.

It is stored as a JSON file attached to a "flowsession" under "additionalcontext".

https://{ENVIRONMENT-URL}/api/data/v9.2/flowsessions({flowsessionid})/additionalcontext/$value

https://docs.microsoft.com/en-us/dynamics365/customer-engagement/web-api/flowsession?view=dynamics-ce-odata-9#properties

https://poszytek.eu/en/microsoft-en/office-365-en/rpa-en/get-power-automate-desktop-runs-details/

If this is a limit we can't change, then disabling certain actions for debugging purpose might be a workaround to keep the history under 9999 entries.

Was this reply helpful? Yes No
Rkv_ 166 on at

Like (1)

Report
@SPCloudguy
Use on block error in the the desktop flow under main and keep all actions within the block.

Create a Subflow getlasterror and add 2 actions Get last Error and Set variable (FailureMessage in the below screenshot must be an output variable)something like below.
Configure the Onblock error to run the subflow getlasterror and go to end of the block.
That's it. if your desktop flow fails then it will return the detailed error message to cloud flow.

I hope you will like this approach.

Was this reply helpful? Yes No
SPCloudguy 111 on at

Like (0)

Report

Hi @fraenK ,

Thank you, whilst it doesn't solve the problem, knowing the cause goes a long way - I initially thought it was an issue with the browser timing out loading the history log, also pleasing to know its not an issue with our tenant/environments.

1000 entries is not a lot though, I've run into this where a flow is processing a report of 600 users carrying out a few actions per user. We have plans for far larger flows, so this is a concern if we're not going to be able to see a full history list.

@Rkv_ , An on error block doesn't help in this instance. I can already see the final error message.

Was this reply helpful? Yes No
adbryson 23 on at

Like (0)

Report

I recently experienced a similar situation and support helped point me to this post.

My issue was also that I could not see the full log history for a Desktop Flow's Action Details (which I was kicking off from a Cloud Flow). The Action Details log would stop showing information and not actually display the final action performed (error or successful completion). This was causing problems for me when trying to troubleshoot any errors that would occur and not get recorded in the log.

The issue was directly related to the number of log entries and once I limited this, the error and completion actions were all displaying in my Action Details screen again.

In my flow, I am using a loop condition to determine when a program has finished opening. After adding a 3 second wait into that loop, the log entries have now been limited enough to fully display my Action Details for each run.

Was this reply helpful? Yes No