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

(6) Share

Report

Posted on by joelzehring

208

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?

Categories:

General topics

I have the same question (0)

All responses (30)

Answers (2)

Sort by

kiki_515 14 on at

Like
a
(2)

Report
Copy link

Link copied!

Same here, this first time I encountered such error too 🙂 and anyone can help to advice how to resolve it? Clearing browser cache, download & history done, but still same warning, I can't edit my flow now...haiz...

Was this reply helpful? Yes No
BelindaBosman 13 on at

Like
a
(2)

Report
Copy link

Link copied!

Yes, same here. Very annoying.

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like
a
(2)

Report
Copy link

Link copied!

This has recently started happening to me too. Clearing browser data doesn't fix it.

Also coincides with the issue when running a child flow. With experimental features turned off or on, the manual trigger appears to have all these metadata parameters (which are not explicitly established in the child flow):

In addition, with experimental features turned on, when I try to dynamically select a variable, the action collapses into an error:

FWIW, with experimental features turned off, it appears to at least let me select a variable dynamically.

EDIT: It's not consistent among flows. Some of them only mark a few of the 'extraneous' parameters as required:

Was this reply helpful? Yes No
HEATFreight 1,024 on at

Like
a
(1)

Report
Copy link

Link copied!
Same thing happening to me! Reset Edge cache with default setting and "all time". Did not fix the problem, but sure as heck was a nightmare to relaunch Edge with probably hundreds of tabs logged into various O365 junk.

I lost all my context! And every focused O365 tab in every window and some of the not-focused tabs as well ask for login creds. But once logged in you can use the browser's back button on extraneous login pages and refresh the content with newly cached credentials, however some tabs get stuck on a login page and the previous URL is lost! Unrelated I know, but really unfortunate side effect of being ADHD and following Microsoft's instructions that they link to in the error:

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

https://go.microsoft.com/fwlink/?linkid=2186936

Was this reply helpful? Yes No
HEATFreight 1,024 on at

Like
a
(2)

Report
Copy link

Link copied!

It seems like all my flows are affected. Even flows which are not Parent or Child flows are affected.

I'm even seeing this affecting flows both within Solutions and flows built outside of Solutions.

Was this reply helpful? Yes No
jmarinuk 37 on at

Like
a
(2)

Report
Copy link

Link copied!

I've also just started seeing this message this week. Clearing the cache/browsing history has not helped. I'm using Edge as my primary browser at work.

Was this reply helpful? Yes No
JWiden297 7 on at

Like
a
(2)

Report
Copy link

Link copied!

I'm also getting this message when trying to edit any Flow on my primary Edge profile. However, if I switch to a different profile or incognito tab I do not. Have tried clearing cookies/cache and restarting to no avail.

Was this reply helpful? Yes No
HEATFreight 1,024 on at

Like
a
(1)

Report
Copy link

Link copied!

More strange behavior like what @Anonymous was seeing...

I have Parent/Child flows failing for broken input schemas, but my Child flow input schemas are all single text inputs (which contain the JSON string of the data I want to pass from Parent flow to Child flow). It's literally looking for exactly one input. But now –only on certain Child flows– I see these extra input fields coming out of nowhere:

I also saw a variation of the collapsed action error when I was trying to edit the formula for the input of a Select action. The mitigation is to directly paste the code using @{function()} notation instead of using the formula editor.

Was this reply helpful? Yes No
larmccoy42 9 on at

Like
a
(2)

Report
Copy link

Link copied!

I have seen the same error. It appears to happen in Chrome, both with and without Ingnito mode. I've also seen this error in Edge one all of my profiles.

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like
a
(2)

Report
Copy link

Link copied!

No response from Microsoft? This seems to be happening suddenly and to a lot of people, and really messes with the development of flows. It'd be nice to get someone to at least officially acknowledge this...

Was this reply helpful? Yes No