Share
ReportHello,
I am working with a flow that connects to an excel document in a SharePoint site. The flow has been working fine previously, for multiple runs. I changed the source document to one with less data, so I could do faster testing of my flow. I ran the flow and it worked successfully and finished much faster. However, the flow is now is bugged and keeps freezing.
When I try to view the run history of this successful run with the smaller excel document, the flow freezes after a few seconds. After refreshing the page, I get the pop-up "microsoft.com is not responding due to a long-running script." If I try to edit the flow and save changes, the flow never finishes saving and I have to refresh the page and I lose changes. This renders the flow almost completely useless, because now I cannot make any edits to it.
This error message exists for both Edge and Explorer, and unfortunately I do not have access to use a different browser. Making a copy of the flow does not get rid of this bug. This happened once before and the only fix I found was to recreate the flow entirely, but this one has now become bugged also. I suppose this is due to changing the source excel document, which I also did the first time, but I don't understand why this would cause my flow to freeze.
Has anyone had any similar issues or know how else to fix this bug other than recreating the flow again? Any help would be appreciated.
All responses (
Answers (
641
