cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
joelzehring
Advocate IV
Advocate IV

Unable to access browser's local storage. Some features such as undo or redo might not work until you clear browser's data

Recently, Power Automate has started to display a warning banner when editing a flow:

 

"Unable to access browser's local storage. Some features such as undo or redo might not work until you clear browser's data."

 

After clearing browser cache and other stored data, this warning still appears.

 

This coincides with an issue where Running a child flow fails because the instant trigger does not have access to location data.

 

Anyone else receive this warning?

 

 

29 REPLIES 29

Have you tried the above mitigation steps? You can get everything working pretty easily if you input arbitrary data wherever your Child-Flow calls are failing.

cortese98
Helper I
Helper I

This is happening on all my flows not just child flows. I have cleared cache multiple times. I am also having connection stability issues since this error message about local cache started.

This is happening on all my flows not just child flows. I have cleared cache multiple times. I am also having connection stability issues since this error message about local cache started.

The error message may be irrelevant. I have learned to just ignore it. The only major issue is that some child flows now have required input fields for their intrinsic location parameters, which you can fix by inputting arbitrary values.

As far as I can see, you can safely ignore the yellow error message about clearing your cache. Clearing your cache will not fix anything in the experience of those posting in this thread.

Certain actions will break if you try to use the function editor, so you directly paste the @{function()} notation instead of editing the formula in the editor.

Other than the function editor breaking and child flow calls breaking, I have not noticed any other major symptoms of this issue.

Tasark
Frequent Visitor

This issue started appearing in my flows, while in Edit mode, over the past few weeks. I will note that I create all of my Flows in a private browser session using a different profile than my personal profile.

 

If I edit the same "shared" flows using my profile in a browser session that is not private, I do not see the error message.

 

Interested if others are only seeing this in a private browser session.

Actually, using a private browser session was noted by the Microsoft support engineer that I spoke with as a mitigation which makes the error go away. It seems that being in the same context as that in which the flow was created leads to the error being displayed, but changing context may cause it to go away.

However, I think the yellow error bar that pops up in your flow editor is meaningless. It's superficial. It may have some deeper significance but it does seem that you can safely ignore it, so long as you know the workarounds for the other two symptoms, which are the broken function editor (fixed by pasting @{function()} notation rather than editing functions in the editor) and the child flow calls requiring their intrinsic location parameters as inputs (fixed by adding arbitrary values to all the blank child flow inputs).

dhock
Kudo Collector
Kudo Collector

This is not only affecting child flows. I do not have any child flows, but all my flows are showing this message. That said, I have not experienced any adverse effects so far, as far as I can tell, but the message is still disconcerting and can lead to unnecessary work to try to resolve it (at least the first time).

briant
Helper I
Helper I

Why is this marked as solved? It is very far from solved, albeit a work around has been presented. Please unsolve it as that is likely why no MS people are looking at it.

Can confirm, nothing to do with parent child and been affecting things for me for past month. Not sure what was changed or why, but they need to fix it.

@briant I agree!

As the person who has the "solution" for this issue, I disagree that it's a solution. It's a workaround. We still see the same issue persist, and neither the instructions in the error itself nor the instructions provided by Microsoft support are sufficient to resolve the issue.

Microsoft need to correct this ASAP. Clearing browser cache is no solution to anything. Firstly, it did not work. Secondly, it's a massive waste of time to be forced to login again when... idk maybe Microsoft could just write good code instead of blaming users for their browser cache? Like pay someone to make this work. Don't screw over your users with tedious fixes that do not even work.

Helpful resources

Announcements
Power Automate News & Announcements

Power Automate News & Announcements

Keep up to date with current events and community announcements in the Power Automate community.

Community Calls Conversations

Community Calls Conversations

A great place where you can stay up to date with community calls and interact with the speakers.

Power Automate Community Blog

Power Automate Community Blog

Check out the latest Community Blog from the community!

Users online (4,766)