User not able to execute flow within the application

Like (3) Share

Report

Posted on 4 Jan 2024 12:05:00 by RobinHenriksen

102

Hi!

I'm having some problems sharing my application with two of my colleagues (or really everyone in my organization). Specifically the two users I've shared my application with recently is not able to execute some of the flows from within the application. When saying not able to execute I mean not able to run the flow at all. However, this does not apply to all of the flows.

All flows etc. are included in the solution.

Data source: Sharepoint

The users get two different error messages.

This user have access to the development environment.
Copydatafromtasklist.Run failed: {"error":{"code":"0x80048306","message":"Principal with id ... does not have ReadAccess right(s) for record with id ... of entity workflow. Details: {\"CallerPrincipal\":{\"PrincipalId\":\"...\",\"Type\":8,\"IsUserPrincipal\":true},\"OwnerPrincipal\":{\"PrincipalId\":\"...\",\"Type\":8,\"IsUserPrincipal\":true},\"ObjectId\":\"...

This user does NOT have access to the development environment.
UpdateCompletecolumninTaskList.Run failed: {"error":{"code":"0x80042f09","message":"RetrievePrivilegeForUser: The user with id ... has not been assigned any roles. They need a role with the prvReadWorkflow privilege."}}

I should add that I have shared this solution / app with two other users before Christmas and it works for them. These two users were also added to the "same" solution in my "Personal Production" environment before I exported the solution to the development environment in mid December. None of these two users have access to the development environment AFAIK.

If I share the flow as "Run-only users" it seems to work. However, I would prefer not to do this for all my individual flows.

The way I understand the documentation it should be sufficient to share a solution with the user and not share each individual flow as well. It is also the way it works for the two previous users I've shared the application with.
https://learn.microsoft.com/en-us/power-apps/maker/canvas-apps/share-app-resources

I've found others struggling with the same issue, and it seems like the way to solve it is to add users to security roles in the environment, but I don't have permission to do this, and I assume it would be better to find another fix if possible.

https://powerusers.microsoft.com/t5/Microsoft-Dataverse/Dataverse-Security-Roles-Solution-with-SharePoint-Canvas-App/td-p/2343509
https://powerusers.microsoft.com/t5/Power-Apps-Governance-and/RetrievePrivilegeForUser-The-user-with-id-id-has-not-been/td-p/1917584

One of my colleagues asked if there was anything special with the flows that this occurs for (which is by the way most of the flows).

My answer to him was.
I'm not sure what is special with the flow which this occurs. I've tested this with one more user now. I got two basically identical flows. One works and the other doesn't. This applies to all three users (initially, I'll explain in the end). They have the same connection references, both linked to the solution etc.

Working flow:

Not working flow:

Working flow:

Not working flow:

When saying it applied to all three users initially i refer to this.

"Another strange behavior I noticed is when I shared one of the flow as "Run only users" it worked for both as expected, then I removed the permission for the two users again, and the flow still worked for one of them (the one outside the environment). Not for the other one though."

I've recreated this with user number two now. I had him as "Run only users", it worked, I removed him again, and it still works. This happened the second time we did this. The first time it stopped working when I removed him from "Run only users". The flow I refer to as the working flow has worked for all three users on the first try without doing anything special.

So by looking at these two flows I'm unable to pinpoint anything that can be causing this problem.

I can also add that user number two changed web browser from chrome to edge after I removed the permission on the "not working" flow, and it still works in edge, so I don't think this weird behavior of the flow working after the permission is removed is related to cookies at least. Maybe the connection fixes itself when they run it with "Run only users" permission, and when I remove the permission the connection continues working.

Categories:

General Questions

Connectors

All responses (17)

Answers (1)

JH-04101654-0 2 on 04 Oct 2024 at 17:00:22

Like (0)

Report

User not able to execute flow within the application

I've experienced the same issue with a managed flow. It was not necessary to remove the flow from the solution. I simply removed the flow from the Power App and then re-connected the flow to the Power App and republished the app. I made sure that the user was running the newly published version of the app and this fixed their roles error.
Suggested answer

Michael E. Gernaey 42,422 Super User 2025 Season 1 on 24 Sep 2024 at 01:25:03

Like (1)

Report

User not able to execute flow within the application

Hi

usually when this happens it means that the Flow is not a Solution Aware Flow. Meaning, that it was NOT in the solution that you imported so it will not auto refresh as it will if you do.

That or someone has made an mistake somewhere. I have seen this over and over and over, when people take a dependency and in the ALM process someone has done something like accidentally important an unmanaged into other environments and then they try to fix it by doing managed etc.

I cannot see yours, but if the flow is doing this, i'd wager someone touched it outside of the Solution.
MRoger 20 on 23 Sep 2024 at 08:57:53

Like (2)

Report

User not able to execute flow within the application

Hi everyone! Long story short, I have the same issue as described above. A solution composed from Canvas App and a Power Automate flow triggered from the app. The solution is shared with EVERYONE in the company. The flow creates new records in a SharePoint list. SharePoint site and List are passed to the flow through environment variable (Data type) to facilitate ALM process. The solution works in Dev environment but starts to complain about users having no security role to rum the flow in the Test environment, where the solution is imported as a managed one.

The problem disappears once the Power Automate flow is refreshed in the Canvas App and the app is re published. While this works, it is breaking the rule where developer should not edit the managed solution, and it also creates an unmanaged layer, that adds complexity to the ALM process.

I have a ticket opened with Microsoft for a week, trying to get a proper solution to this issue, and while I spoke to numerous agents, they all stating that a user must have a proper security role assigned.

Is there anyone in here who had contacted Microsoft regarding this issue?
sbroud 69 on 28 Jul 2024 at 23:50:49

Like (1)

Report

User not able to execute flow within the application

Hi Folks,

I have the same issue. I did remove and reattach the flow to the app. It is always not working under other users' account.

Please help.

Thank you
HaydenSinclair 99 on 23 Jul 2024 at 04:30:51

Like (3)

Report

User not able to execute flow within the application

Adding a user as the owner of the flow seems to fix the errors. But obviously it doesn't feel like the best way to overcome the issue.

These solution related issues can waste days and days. Microsoft seem to be making changes and improvements which is great. I can only hope they use solutions themselves so they can share the pain and come up with a better methods of making them work.
ajetani 9 on 16 Jul 2024 at 08:52:31

Like (1)

Report

Re: User not able to execute flow within the application

@Oskarkuus - Did you find a solution for this? I'm also facing the same issue.
ajetani 9 on 16 Jul 2024 at 08:50:24

Like (1)

Report

Re: User not able to execute flow within the application

Hi @RobinHenriksen , I'm facing the exactly same error after deploying my Power App using Azure DevOps. I'm deploying it as a managed solution so I'm not able to edit the app. Can you kindly provide exact steps you followed to refresh the flow from within the application in a managed solution. The link you shared doesn't mention anything about refreshing the flows from within the application.

Can you please help me here? I'm really stuck at this point 😞
juan-becerra 4 on 22 May 2024 at 13:48:28

Like (1)

Report

Re: User not able to execute flow within the application

Thanks Robin!, this was very helpful 🙂
Oskarkuus 1,095 on 09 Apr 2024 at 18:03:37

Like (1)

Report

Re: User not able to execute flow within the application

I have this issue and i can not get any solution to fix this.

the error is:
TeamsyncDeleteTeam.Run misslyckades: {"error":{"code":"0x80048306","message":"Principal with id 3537d5d3-83f6-ee11-a1fd-000d3a39b91a does not have ReadAccess right(s) for record with id 58deb769-4ede-ee11-904c-000d3ab24d75 of entity workflow. Details: {\"CallerPrincipal\":{\"PrincipalId\":\"3537d5d3-83f6-ee11-a1fd-000d3a39b91a\",\"Type\":8,\"IsUserPrincipal\":true},\"OwnerPrincipal\":{\"PrincipalId\":\"2314af6b-0605-ee11-8f6e-000d3a49c465\",\"Type\":8,\"IsUserPrincipal\":true},\"ObjectId\":\"58d...

I have tried
1. Remove the whole solution and import it as new.
2. Go to the application in dev enviroment and update the flow in the app
3. Remove the flow fro the app in dev enviroment
4. Recreate the flow and add it as a brand new flow to the app in dev enviroment.

Nothing works.

The only thing that works is to create a custom layer in the Production enviroment and go into the app and resave the application after updating the flow.

But i cant have this as a solution since the application need to be able to update constantly from the dev enviroment and i cant have custom layers in the production enviroment.

How to fix this?
luginaqolbyj 3 on 21 Mar 2024 at 04:20:34

Like (1)

Report

Re: User not able to execute flow within the application

Hi,

it also happened to me, and I tried your solution to refresh the flow in the app. It works like a charm! Thank you.