Flow run history - Unexpected error. Unable to fetch

[ChristianStep]

Hi,

my flow runs successfully 

Now I want to check some data inside the flow and browse through this loop... looking fine

But for some unknown reason a few runs are showing this error - and it went successful...?!

Opening the mentioned URL is showing me the output which should be shown in the history area ?!

So is there an internal error or something?

At first I thought my flow had an error and this action failed. But data in lists are fine ... so just the history has a bug?!

Anyone else saw this? Any chance to see full history or even export them?

Thanks and Regards,

Christian

[efialttes]

Hi!

I guess "Unable to fetch" means a timeout ocurred when Flow Run History page tried to get back details from Microsoft Cloud, since you can access them through the browser when typing the URL directly.

You can export Run History as CSV
https://flow.microsoft.com/en-us/blog/download-history-recurrence/

Hope this helps

[ChristianStep]

Hi!

Good to know 🙂 Was not aware of this function.

But still anoying while browsing through the online history ... 😕

[KoalaKev]

When I have seen these "Unable to Fetch" errors on successful flow runs, it is due to the fetching the data of the Flow Run report.  Refreshing the page will usually resolve those fetch errors and you will be able to review your Flow run report data.

[johnguilbert191]

This happens a lot. Even after refreshing the page you may have to wait a good while before you expand action. Ridiculous. This should have a highlight on the action bar that does not allow it to be expanded until it has loaded. Message in highlight bar should be "Awaiting server data fetch...".    

[Kees-OfficeKeys]

@johnguilbert191 , thanks for the tip on waiting before expanding! This at least solved the very annoing error. I rather wait one minute before expanding then constantly downloading the raw input and raw output.

[minhvo]

Thanks for sharing. It is very helpful for me to review the flows.

[johnguilbert191]

Actually, best way to fix this is copy the link of the flow in edit mode. Close Browser. Open Browser and paste link. This should then show details every time. Reason it fails is due to viewing all runs and selecting flow from list. Takes time as I think it loads all flows details in list which may take some time. 

[Anonymous]

THIS! finally! I copied and pasted into another browser and Failed to Fetch was gone. thank you!!

[Nick_McEwen]

I have wasted hours on this .. thanks for posting the answer here .. it works every time now
Just copy the link and paste in a new tab

[PaulColucci]

Absolutely Awful

[whitelc]

I'm having the same problem. It started within the last month or so. The suggestion to copy the URL and open in another browser. works. I work in Chrome. Run history displays correctly when I open the URL in Edge. I contacted Microsoft support. Their typical useless answer was to use Edge. Sigh.

Reminds me of a joke. Man says, "Doctor, it hurts when I do this." Doctor replies, "Then don't do that."

[StanDiamond]

I'm also getting this annoying and time-wasting problem that makes it tedious to debug flows with Apply to Each actions.  My default browser is Edge and I've tried Firefox, and also the suggestion to upen in a new tab.  Nothing works.  Please Microsoft fix this.

[HansenvomDeich]

same here...