Error When Trying to Open Successful Flow: "Cannot read properties of undefined (reading 'config')"

[sdedic]

Hi all,

This is becoming worrisome and challenging to keep up with what Microsoft is doing with its changes, and I believe I'm not the only one who thinks so. In the past few weeks, we've had so many sudden breakdowns of Power Apps applications and Power Automate flows that were working flawlessly up until that point. Without any changes, these same applications and flows would start throwing errors, Microsoft would impose changes without warning in production environment (adding Dataverse Accelerator app), and so on.

What greeted me this morning was an error: 'Cannot read properties of undefined (reading 'config'),' and that happened when I selected a flow that had executed successfully. As you can see in the image below:

Error:

I need to check some steps inside the flow and see the output of some actions, but as you can see the flow won't open and it throws the error - all of a sudden - amazing!

From sudden changes and imposition of applications, to undefined request limits that come with licenses, Microsoft is providing an unforgettable experience.

Hope someone will have answer to this, desirably someone from MS.

Best

[Bambula]

I'm experiencing similar issues, and the Dataverse Accelerator app has caused some problems in my environment. 

[Kaif_Siddique]

Try to recreate connections for connector.

[sdedic]

Ty for suggestion @Kaif_Siddique,. However, this is something I can't do since the app/flow is in the production and it's working fine. Recreating connections implies importing new version from dev to prod which is not feasible at this time. It also doesn't guarantee that the issue will be resolved since the flow is being successfully finished each time. The only problem is that I can't access the finished flow and investigate outputs from actions.

Hopefully someone from MS will come upon this and provide proper answer why something like this is happening in the first place.

[joedl]

I'm having similar difficulties when creating a new flow and using Sharepoint connector to list files from Sharepoint file library. Getting an 'Cannot read properties of undefined (reading 'config'),' error when trying to test the flow.

Found MO682290 in Service health: "

Users may see failures occurring for some workflows and lists in multiple services". Could this be the reason for this error?

[Mel1Mel0]

I'm experiencing the sames issue and reconnection of connectors does not help at all.

[Sharma_Ankit]

Hi sdedic,

I have started to face the same issue after the new updated flow viewer. I switched back to classic view in you and the issue got resolved.

Please try the same and let me know if this works for you as well or its just a fluke at my end.

[Jfranz]

Yesterday I was working in Power Automate (Nov 14 2023) with no issues. I have ignored the "Use New Designer" for awhile now. But today that option was gone and I was forced into the new designer which is buggy as hell. But now when I go to my runs I can't get in to see anything anymore. This is a major problem and is happening on ALL my flows no matter the owner/connectors/complexity. We have 100s of flows and everyone of them is having this issue. This needs a fix ASAP!

[FlamingNinja173]

As an FYI, you can still Access the old designer if you access your flow via PowerApps. Open your solution while on the powerapps site (purple borders, not blue) and you can still use the old designer.

[FlamingNinja173]

I was having this issue. I went and saved the flow using the old designer, and the error went away. All I changed was the description of a parameter.

MS, I like the new designer overall, but you can't make it the only option when there are critical issues with it.

[Jfranz]

Thanks for this! Saved me a lot of stress, until they take that away too.

[LASMA]

Clear your cookies in your browser. Worked perfectly for me. I did not succeed when changing to Classic mode, but got an error page, that I could not remove and had to delete the entire flow recreating it.

[wangzhenassd]

Thanks a lot! I faced the same issue and solved it with the way you suggested.

[arevaloc]

Thanks, it worked perfectly for me too.

[Noidontthinkiwi]

Edge was the problem for me. Tried chrome and everything went fine. YMMV...

[HaiHT1234]

I met the same problem