I was already getting depressed, I can't believe it was so easy. Ty so much.
When I was faced with this issue, there was a previous custom connector connection I had overlooked, and just had to delete that as it was not in-use (while also removing the flow from the app as a safety measure as well). Don't forget to rule out the small stuff!
We've been struggling with the same error for quite some time, but we're glad to have finally found its root cause.
The error follows a distinct pattern: it emerges when using a single automated flow across two different applications, particularly when configuring the same flow in multiple apps with different underlying connections.
By 'different underlying connections,' I mean users utilizing various Microsoft accounts.
For instance, in App_1, the flow is configured using abc@xyz.com,
while in App_2, it's configured using qwe@xyz.com.
This discrepancy causes ambiguity, leading the flow to struggle when making API calls.
The question then arises: Can we use a single automated flow in different PowerApps?
Yes, it's possible.
Solution-:
The solution involves ensuring that a flow 'FLOW' integrated/used in multiple PowerApps like 'App_1' and 'App_2,' is connected to underlying connections (such as SQL or SharePoint) using the same Microsoft account. This consistency in underlying connections (SQL or SharePoint) is crucial to prevent these errors.
Hope this helps in resolving the issue. Happy learning!
Same issue today.
I was about to follow the "solved solution", and before removing powerautomate connector, I clicked on modify from PowerApps.
Then, I did nothing else than close the PowerAutomate embeded window.
I tried again my apps and it works !
culun lu kaya temen gw iman
Thank you, that worked! I needed to refresh the App after those 2 steps, but I'm now back in business. Thanks again.
Rename the flow and save. Should work after that
What an absolute crock of sh*t everything to do with Power Platform ALM is. Microsoft should be ashamed of themselves pushing this half-baked cr*p on us.
Remove and re-add the Flow in the App solved the issue for me
WarrenBelz
146,660
Most Valuable Professional
RandyHayes
76,287
Super User 2024 Season 1
Pstork1
66,004
Most Valuable Professional