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?
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.
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://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.